KLXS_III_RFP_Portfolio.pdf

PDF 5 MB Posted

Attached to
KLXS III Award Federal contract opportunity
Solicitation number
80KSC018R0006
Issued by
National Aeronautics and Space Administration Kennedy Space Center

About this file

KLXS III RFP Portfolio (excludes pricing templates)

View the file

Other files for this federal contract opportunity

Other files attached to KLXS III Award, newest first.
File Type Posted
KLXS_III_RFP_Responses_to_Questions_5.23.2018.pdf PDF
KLXS_III_-_Amend_4.pdf PDF
KLXS_III_RFP_Responses_to_Questions_5.17.2018.pdf PDF
KLXS_III_-_Amend_3.pdf PDF
KLXS_III_RFP_Responses_to_Questions_5.10.2018.pdf PDF
L-04b_KLXS_III_Basic_Cost_Template_(Amendment_2).xlsm XLSM spreadsheet
KLXS_III_-_Amend_2.pdf PDF
KLXS_III_-_Amend_1.pdf PDF
L-04b_KLXS_III_Basic_Cost_Template_(Amendment_1).xlsm XLSM spreadsheet
L-04b_KLXS_III_Basic_Cost_Template.xlsm XLSM spreadsheet
L-04c_KLXS_III_Rates_and_Factors_Template.xlsm XLSM spreadsheet
L-04a_KLXS_III_Phase-In_Template.xlsm XLSM spreadsheet
Show all 12

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

Cover Sheet

80KSC018R0006

KLXS III RFP

ATTACHMENT J-16

SUBCONTRACTORS

AND

TEAMING PARTNERS

LIST

[PAGE INTENTIONALLY LEFT BLANK]

J-16

80KSC018R0006 Subcontractors and Teaming Partners List

KLXS III RFP Attachment J-16

The list below represents all subcontractors/teaming partners associated with performing work under KLXS III.

Subcontractor
NameContract
TypeSubcontract

Size

(Major/Minor)Business
ClassP or S
(Note 1)PWS

Areas at the Sub Level % of each individual PWS area worked Has Completed a full cost template workbook (Y/N) Has Provisional Billing Rates in Table B.8-1 (Y/N) Other Comments

Ex 1 ABC, Inc. CPFF Major Large P 1.1 Y Y

Ex 2 XYG, Inc. T&M Minor SDB S 3.3 N N

Ex 3 XYG, Inc. T&M Minor SDB P 4.2 N N

Note 1: P = Prime Responsibility

S = Secondary Responsibilities

Add an adjacent separate row(s) immediately below if subcontractor performs functions on more than one PWS area

To be completed as part of the model contract.

To be updated during contract administration, in accordance with Clause H.21, to reflect the current teaming arrangements or subcontractors.

Add or delete rows as necessary.

[PAGE INTENTIONALLY LEFT BLANK]

Page &P of &N Attachment J-16

80KSC018R0006

KLXS III RFP

ATTACHMENT J-17

ACRONYMS AND GLOSSARY

[PAGE INTENTIONALLY LEFT BLANK]

KLXS III RFP Acronyms and Glossary Attachment J-17

Page 1 of 18 Attachment J-17

Table of Contents

Acronyms………………………………………………………………………………….. 3

Glossary …………………………

A B C D E F G H I J L M N O P Q R S T V W

Page 2 of 18 Attachment J-17

Page 3 of 18 Attachment J-17

ACRONYMS

ACA Associate Contractor Agreement ACES Agency Consolidated End-user Services ACO Architecture and Concept of Operations ADP Acceptance Data Package ARM Active Risk Management ASCS Agency Security Configuration Standards ASUS Agency Security Update Services BER Best Estimated Rate C3PW Contractor 3rd Party Work CCB Configuration Control Board CDR Critical Design Review CEA Center Export Administrator CFR Code of Federal Regulations CIO Chief Information Officer CLIN Contract Line Item Number CM Configuration Management CMA Contract Management and Administration CO Contracting Officer CoF Construction of Facilities CoFR Certification of Flight Readiness ConOps Concept of Operations COOP Continuity of Operations Planning COR Contracting Officer’s Representative CPFF Cost Plus Fixed Fee CPIT Cross-Program Integration Team CR programmatic Change Request DCR Design Certification Review DDMS Document and Data Management System DES Discrete Event Simulation DM Data Management DoD Department of Defense DRD Data Requirement Description EAR Export Administration Regulations eCC Electronic Country Clearance ECP Export Control Plan EGS Exploration Ground Systems EM Exploration Mission EOM Element Operations Manager EPM Element Project Manager ER Eastern Range ESD Exploration Systems Development EVM Earned Value Management EVMS Earned Value Management System FAA Federal Aviation Administration FICA Federal Insurance Contributions Act FISMA Federal Information Security Management Act FM Financial Management

Page 4 of 18 Attachment J-17

FRR Flight Readiness Review FY Fiscal Year GAO Government Accountability Office G&A General and Administrative GFY Government Fiscal Year GHMT Ground Hardware Management Tool GSDO Ground Systems Development and Operations GSE Ground Support Equipment HEO Human Exploration and Operations HERSP Human Exploration Range Safety Panel HF Human Factors HOTH Houston Orion Test Hardware HSI Human Systems Integration IAGP Installation-Accountable Government Property ICD Interface Control Documents ICE Integrated Collaborative Environment ICM Information and Configuration Management IDIQ Indefinite Delivery Indefinite Quantity IPCA Integrated Physical Configuration Audits IPCWG Integrated Programmatic Communication Working Group IPIT Integrated Programmatic and Program Control Integration Team IRD Interface Requirements Document IRWG Integrated Risk Working Group IT Information Technology ITAR International Traffic in Arms Regulations ITL Integrated Test Laboratory ITSEC-EDW IT Security Enterprise Data Warehouse JCL Joint Confidence Levels JSC Johnson Space Center KDP Kennedy Documented Procedures KLXS III Kennedy LX Support Services Contract - III KNPR Kennedy NASA Procedural Requirements KNPD Kennedy NASA Policy Directive KPRD Kennedy Progra Requirements Document KSC Kennedy Space Center LCC Launch Commit Criteria LM Lockheed Martin LSA Logistics Support Analysis LSAIB Launch Site Assembly and Integration Baseline LX Exploration Ground Systems Program Office MD Mission Directorate MSFC Marshall Space Flight Center NASA National Aeronautics and Space Administration NEC Negotiated Estimated Cost NF NASA Form NPD NASA Policy Directive NPR NASA Procedural Requirement NSSC NASA Shared Services Center

Page 5 of 18 Attachment J-17

O&M Operations and Maintenance O&TM Operations and Test Management OCSO Organizational Computer Security Officer OCSR Organizational Computer Security Representative ODC Other Direct Cost OH Overhead OIG Office of Inspector General OMB Office of Management and Budget OMRS Operations and Maintenance Requirements and Specifications ORR Operations Readiness Review PDR Preliminary Design Review PHS&T Packaging, Handling, Storage and Transportation PII Personally Identifiable Information PMT Performance Management Team PMTA Program Milestone Tracking Analysis POC Point of Contact PP&C Program, Planning and Control PPBE Planning, Programming, Budgeting and Execution PRD Process Requirement Document PSI Programmatic and Strategic Integration PWS Performance Work Statement QRA Quantitative Risk Analyses RC Reporting Category REEB Resource Environment for Enhanced Budgeting RFA Request for Action RFP Request for Proposal/Procurement RID Review Item Discrepancy RMA Reliability, Maintainability and Availability S&MA Safety and Mission Assurance SAR System Acceptance Review SBU Sensitive But Unclassified SDB Small Disadvantaged Business SDLC System Development Life Cycle SEC Security SE&I Systems Engineering and Integration SEMO Supply and Equipment Management Officer SEMP Systems Engineering Management Plan SIL Systems Integration Lab SIR System Integration Review SLS Space Launch System SOP Standard Operating Procedures StE Stakeholder Expectations TIM Technical Interchange Meeting V&V Verification and Validation VAB Vehicle Assembly Building VEBA Voluntary Employees Beneficiary Association WBS Work Breakdown Structure WYE Work Year Equivalent

Page 6 of 18 Attachment J-17

Page 7 of 18 Attachment J-17

GLOSSARY

A

ACCEPTANCE DATA PACKAGE (ADP): The specific data in a single package which contains information pertinent to acceptance, and provides a verified status, including the as-built configuration (software or hardware) to the using organization. The ADP is prepared as part of the hardware or software acceptance/delivery criteria and maintained throughout the hardware or software life cycle after Government acceptance, including processing; testing; launch on-orbit and post-landing processing; and maintenance, modification, and refurbishment activities.

ACCESS CONTROL: Limiting access to hardware, equipment, information or operations for the purposes of maintaining one or more of the following: safety, quality, configuration and item integrity.

ACCREDITED INSTITUTION: A post-secondary educational institution (e.g., college or university) which was approved by an accrediting agency listed as nationally recognized by the U.S. Department of Education.

ACTIVE RISK MANAGEMENT (ARM): EGS risk management tool.

AGENCY (uppercase 'A'): National Aeronautics and Space Administration (NASA)

APPROPRIATION: A provision of law authorizing the expenditure of funds for a given purpose, usually, but not always, in an appropriations act. It is designated by the Treasury Appropriation Fund Symbol (TAFS).

ASSOCIATED CONTRACTOR AGREEMENT (ACA): A documented mutual understanding between two or more contractors that enables support from one to the other or working together to meet a common objective and requiring minimal (if any) Government involvement.

AVAILABILITY: The probability that an item is in an operable and committable state when called for at an unknown time.

B

BASELINE (Engineering): The defined and approved end-item configuration that is documented by drawings, specifications, and/or other technical documents. A reference for program and project planning and a point of departure for change control.

C

CENTER (uppercase 'C'): John F. Kennedy Space Center (KSC).

CERTIFICATE OF FLIGHT READINESS (CoFR): The process and documents that certify flight hardware, personnel, and supporting systems are ready to support flight milestones.

Page 8 of 18 Attachment J-17

CERTIFICATION: The formal written act whereby a responsible official attests to the satisfactory accomplishment of specified activities and authorizes the affected hardware/ software, procedures, facilities, and/or personnel for specified usage.

CHANGE REQUEST (CR): (programmatic Change Request) Document that defines a proposed change to the EGS, SLS, Orion, or ESD Technical Baseline. This document initiates a review of potential technical, cost, schedule or risk impacts that may result from the proposed change.

CLOSEOUT: The process of inspecting and securing hardware, usually flight hardware, to ensure no foreign material, damage or out-of-configuration condition exists prior to covering an area in preparation for testing or flight.

COMPLIANCE: The act or process of satisfying requirements.

CONFIGURATION CONTROL: A systematic change process for proposing, justifying, evaluating, coordinating, disposing, and implementing proposed baseline changes.

CONFIGURATION MANAGEMENT: A process that establishes and maintains consistency of a product's attributes with its requirements and product configuration information throughout the product's life cycle.

“CONSISTENT WITH” (as used in the PWS): The contractor has some flexibility to develop and apply an approach, but the approach must meet the intent of the reference document.

CONSTRAINT: Any technical or operational limiting factor that would prohibit performance of an activity, invalidate a portion of a work authorization document (sequence or step), or could cause personal injury or equipment damage if not resolved satisfactorily before the start of the work sequence or step.

CONSTRUCTION OF FACILITIES (CoF): NASA's capital investment program for facility projects with estimated cost of greater than $1,000,000 per project. CoF projects are approved by NASA Headquarters and require Congressional approval.

CONTINGENCY: A potential off-nominal operational condition that requires action.

CONTRACTOR: The term “Contractor” as used herein refers to both the prime Kennedy LX Support Three (KLXSIII) Contractor and any KLXSIII subcontractors.

CONTRACTOR (lower case “c”): The term “contractor” as used herein refers to any person or company that undertakes a NASA contract to provide materials or labor to perform a service or do a job.

CONTRACTING OFFICER (CO): The individual appointed by the contracting activity for procuring and/or administering a contract. The CO is the only person authorized to direct contractor performance, execute amendments to the contract, and contractually obligate the Government.

Page 9 of 18 Attachment J-17

CONTRACTING OFFICER’S REPRESENTATIVE (COR) (FORMERLY CONTRACTING

OFFICER’S TECHNICAL REPRESENTATIVE – COTR): A Government official who has been appointed by the CO who has the responsibility in managing the technical aspects of the contract and monitor the Contractor’s technical performance and delivery of the final products and/or services. The COR and Alternate COR (who may only act in the COR’s absence) are the only Government officials other than a CO who may give technical direction to the Contractor.

Pursuant to NFS 1842.270, the COR is not authorized to initiate procurement actions or in any way cause a change to the contract or increase the Government's financial obligations.

CORRECTIVE ACTION: Action(s) taken to eliminate the root cause of a problem to prevent its recurrence.

CRITICAL: The categorization based on the worst case potential effect of failure (loss of function or inadvertent operation), that could result in loss of life, loss of vehicle, or damage to a vehicle systems. (See KNPR 8700.2)

CRITICAL PATH: The minimum series of tasks within a schedule that define the overall duration of the project or Program. A change in the duration of a task within the critical path will cause a corresponding delay or acceleration of the entire project or Program.

CROSS-CUTTING: Functions or tasks that span across all aspects of the EGS Program to achieve its technical baseline.

CROSS-PROGRAM: Refers specifically to the Space Launch Systems (SLS), Orion, and EGS Program(s).

CROSS-PROGRAM INTEGRATION TEAM (CPIT): Team established by the ESD programs to discuss technical designs, issues, and concerns with all stakeholders from each program included.

CROSS-PROGRAM SYSTEMS INTEGRATION (CSI): One of the two entities that has authority, accountability and responsibility for cross-Program integration. CSI maintains cognizance of the technical performance of the integrated system and consists of members from Exploration Systems Development (ESD) and the three (SLS, Orion, and EGS) Programs through multiple Integrated Technical Teams and Working Groups.

D

DATA MANAGEMENT (DM): Part of the Information Management System that includes developing a data strategy, determining specific data requirements, authenticating data requirements, and developing DM processes to ensure the integrity of the Information Management System.

DATA REQUIREMENTS DESCRIPTION (DRD): A detailed description of a required data item including purpose, content, format, references, maintenance requirements, submittal requirements, and other pertinent information.

DATA REQUIREMENTS LIST (DRL): A list of DRDs applicable to this contract.

Page 10 of 18 Attachment J-17

DECISION PACKAGE (DP): Documentation used during the budget planning process to identify content exceeding baseline funding. The documentation includes budget and schedule impacts.

“DEVELOP AND MAINTAIN”: The Contractor is required to develop or provide an approach/product and provide the necessary resources to sustain/update/revise that approach/product as required.

DOCUMENTATION: Information and its supporting medium (e.g., records, specifications, drawings, reports, standards and work documents). The medium may be paper, photography, digital files, optical discs, magnetic, electronic storage or a combination.

E e533 FLAT FILE: A format specific machine readable electronic file of NASA Form 533 reportable data.

EARNED VALUE MANAGEMENT (EVM): A project and program management technique for measuring project and program performance and progress in an objective manner.

EARNED VALUE MANAGEMENT SYSTEM (EVMS):..An integrated management system and its related subsystems that allow for planning all work scope to completion; assignment of authority and responsibility at the work performance level; integration of the cost, schedule, and technical aspects of the work into a detailed baseline plan; objective measurement of progress (earned value) at the work performance level; accumulation and assignment of actual costs;

analysis of variances from plans; summarization and reporting of performance data to higher levels of management for action; forecast of achievement of milestones and completion of events; forecast of final costs; and disciplined baseline maintenance and incorporation of baseline revisions in a timely manner.

EASTERN RANGE (ER): An area in which rockets are fired for testing and tracking. Cape Canaveral serves as the range’s space processing and launch area, and the Air Force controls the range for all eastern-bound launches. The range starts at the launch pads at Cape Canaveral Air Force Station and Kennedy Space Center (KSC) and extends eastward over the Atlantic Ocean and into the Indian Ocean.

ELEMENT: Major functional components of each EGS functional team.

ELEMENT OPERATIONS MANAGER (EOM): The Operations Manager for each of the Element Integration Teams (EITs). The EOMs bring operational expertise to the team and co-leads each EIT along with the EPM.

ELEMENT PROJECT MANAGER (EPM): The development Project Manager for each of the EITs. The EPMs bring developmental project expertise to the team and co-leads each EIT along with the EOM.

ELEMENT SCHEDULES: Detailed schedule managed by the EGS Elements.

Page 11 of 18 Attachment J-17

ELEMENT TO ELEMENT: Integration activities between Element teams.

EQUIPMENT: A tangible asset that is functionally complete for its intended purpose, durable, nonexpendable. Equipment is not intended for sale, and does not ordinarily lose its identity or become a component part of another article when put into use.

EXPLORATION GROUND SYSTEMS (EGS): (formerly known as the Ground Systems Development and Operations Program). EGS is responsible for the cost, schedule, and technical content of launch systems development and launch vehicle and spacecraft processing for the Orion, Space Launch System (SLS), and future Human Exploration and Operations payloads or spacecraft using the SLS. EGS develops the ground systems and ground operations processes to perform ground operations at the launch, landing, and recovery sites required to accomplish receiving, ground processing, assembly and integration, integrated and interface testing, launch operations, recovery and retrieval, deintegration, refurbishment, pad abort, and search and rescue /retrieval operations.

EXPLORATION SYSTEMS DEVELOPMENT (ESD): A Division within Human Exploration and Operations (HEO) Mission Directorate (MD) (HEOMD) that integrates a portfolio of Programs comprising incrementally developed exploration capabilities. ESD manages the SLS, the Orion, and the EGS Programs as well as cross-Program integration in order to successfully deliver the capabilities required for human spaceflight beyond low Earth orbit.

EXTERNAL CUSTOMER: An outside organization or individual that receives a product or service.

F

FISCAL YEAR (FY): The US Government accounting year for appropriations which is the 12-month period starting October 1st and ending September 30th.

FLIGHT ELEMENT: Major flight functional components of a Program such as payload, spacecraft, or booster. Flight elements may contain a subset of flight systems projects.

FULL ACCESS (read only): Capability for the Government to obtain on-line, network accessible interface with the Contractor’s computer system or software application to view data.

FULL ACCESS (read/write): Capability for the Government to obtain on-line, network accessible, interactive interface with the Contractor’s computer system or software application to view and data entry capability.

FUNCTIONAL TEAM: A multidisciplinary group of individuals with appropriate domain knowledge, experience, competencies, and skills related to a specific subject matter. Team provides integrated products and perform day-to-day tasks, with participation from the Program and KSC institutional organizations. This team is a subset of the PMT with a discrete area of focus responsible for mission deliverables.

Page 12 of 18 Attachment J-17

G

GOVERNMENT-FURNISHED PROPERTY (GFP): Property in the possession of, or directly acquired by, the Government and subsequently made available to the contractor.

GOVERNMENT PROPERTY: All property owned or leased by the Government. Government property includes both GFP and contractor-acquired property. This includes installation-accountable and contractor-accountable property as pursuant to NFS 1852.245-71 and FAR 52.245-1, respectively.

GROUND ELEMENT: Major non-flight functional components of a Program. Ground elements may contain a subset of ground systems projects. The EGS ground elements are depicted in the GSDO-PLN-1000, EGS Program Plan.

GROUND SUPPORT EQUIPMENT (GSE): Non-flight equipment, systems, or devices specifically designed and developed for a direct physical or functional interface with flight hardware.

GROUND SUPPORT SYSTEMS (GSS): Infrastructure and equipment (portable or fixed) that provide functional and/or physical support to GSE. GSS does not directly interface with flight hardware, although GSS may supply commodities, power, or data that eventually reaches the flight hardware after being conditioned or controlled by GSE.

GROUND SYSTEMS: Systems used to process or test flight hardware during ground processing, including unique facility systems, GSS, GSE, and flight hardware special test equipment.

GROUND SYSTEMS DEVELOPMENT AND OPERATIONS (GSDO) PROGRAM: See Exploration Ground Systems (EGS).

H

HUMAN EXPLORATION AND OPERATIONS (HEO) MISSION DIRECTORATE (MD)

(HEOMD): At NASA HQs, the HEO Associate Administrator (AA) is responsible for managing commercial crew and cargo developmental programs; construction of the Orion (a spacecraft designed to travel beyond Low Earth Orbit [LEO]); development of a new heavy-lift rocket (SLS);

development of flight and ground infrastructure and systems and other programs with the directorates.

HUMAN SYSTEMS INTEGRATION (HSI): An interdisciplinary and comprehensive management and technical process that focuses on the integration of human considerations into the system acquisition and development processes to enhance human system design, reduce life-cycle ownership cost, and optimize total system performance. Human system domain design activities associated with manpower, personnel, training, human factors engineering, safety, health, habitability, and survivability are considered concurrently and integrated with all other systems engineering design activities.

Page 13 of 18 Attachment J-17

I

“IN ACCORDANCE WITH”: The Contractor shall comply with all aspects (requirements, guidelines, specifications, etc.) of the associated compliance document.

INDEPENDENT ASSESSMENT(S): (includes reviews, evaluations, audits, analysis oversight, investigations). Assessments are independent to the extent the involved personnel apply their expertise impartially and without any conflict of interest or inappropriate interference or influence, particularly from the organization(s) being assessed.

INSTITUTIONAL: KSC organizations providing direct support to the EGS Program such as, Engineering, Safety and Mission Assurance (S&MA), Information Technology, Spaceport Integration, Center Planning and Development.

INTEGRATED PHYSICAL CONFIGUATION AUDITS: A configuration management process which is an examination of the actual “as-built” configuration of a piece of hardware or software and compares it against the technical documentation to verify the item’s product baseline.

INTEGRATED MASTER SCHEDULE (IMS): A logic network-based schedule that reflects the total project scope of work, traceable to the WBS, as discrete and measureable tasks or milestones and supporting elements that are time phased through the use of valid durations based on available or projected resources and well-defined interdependencies.

INTERFACE CONTROL DOCUMENT (ICD): Documentation that defines the specifications, drawings and written record for each side of an interface between different contractors, NASA Programs, and/or Government agencies. The information defined in the ICD is necessary to implement the functional requirements defined by the IRD.

INTERFACE REQUIREMENTS DOCUMENT (IRD): Documentation that identifies the functional requirements between different NASA Programs, contractors, and/or Government agencies.

J

JOINT CONFIDENCE LEVEL (JCL): (1) The probability that cost will be equal to or less than the targeted cost and schedule will be equal to or less than the targeted schedule date. (2) A process and product that helps inform management of the likelihood of a project’s programmatic success. (3) A process that combines a project’s cost, schedule, and risk into a complete picture.

L

LAUNCH COMMIT CRITERIA (LCC): Critical factors used to determine final decision to launch, in this case specifically for the integrated SLS launch vehicle.

LIFE CYCLE: The term “life cycle” as used herein refers to Program and project life cycles as defined in NPR 7120.5, NASA Space Flight Program and Project Management Requirements.

LOGISTICS SUPPORT ANALYSIS (LSA): A disciplined and structured approach, highlighting actions to define, analyze, and quantify logistics support requirements, and to influence design for supportability throughout system development.

LX: The NASA KSC mail code for the EGS Program Office.

Page 14 of 18 Attachment J-17

M

MAINTAIN (DOCUMENTATION): The process of ensuring that a document is configuration-controlled and current.

MISSION: The performance of a coherent set of operations to achieve Program goals.

MISSION ASSURANCE: Activities or the performance of activities which provide increased confidence that the requirements, processes, and standards for a mission are being fulfilled.

MISSION DIRECTORATE (MD): A primary implementer of a NASA mission area. Each MD is led by an Associate Administrator who leads their respective mission area.

MODIFICATION: Any change to the configuration of the facility resulting in the update to the current capabilities and services, expansion of existing capabilities and services, or the addition or deletion of existing capabilities and services.

N

NASA-MANAGED PROJECT: Any project where the Government has the overall management responsibility.

O

OFFICE OF PRIMARY RESPONSIBILITY (OPR): An organization with overall responsibility for the development of, and subsequent changes to, a designated document or function.

OPERATIONS AND MAINTENANCE REQUIRMENTS AND SPECIFICATIONS

(OMRS): Cross-program approved requirements levied upon EGS for implementation of ground processing and integration of the flight elements and Ground Support Equipment (GSE) supporting launch readiness of the integrated vehicle. OMRS will be used to communicate detailed processing requirements to be implemented via work instructions.

ORION/ORION PROGRAM (Formerly Multi-Purpose Crew Vehicle – MPCV): The spacecraft being designed and developed by the Orion Program. The Orion Program, assigned to the Johnson Space Center (JSC), is responsible for developing a spacecraft, including the crew capsule that supports long-range human exploration needs. The Program is charged with the design and development of the crew vehicle and associated elements such as extra vehicular activities (EVA) systems, flight crew equipment, and mission operations.

OVERSIGHT: An element of Government surveillance that occurs in line with the contractor's processes in which the Government retains and exercises the right to concur or nonconcur with the contractors' decisions.

Page 15 of 18 Attachment J-17

P

PAYLOAD CUSTOMER: The organization responsible for overall design, fabrication, integration, and operation of the payload. Assumed to include such people as program managers, payload developers, and principal investigators.

“PER”: See "In Accordance With".

PERFORMANCE MANAGEMENT TEAM (PMT): The top level EGS functional management team tasked with ensuring that EGS Functional Teams meet Program milestones and mission commitment dates, the Functional Teams (e.g., Ground Systems Implementation (GSI), Command, Control, and Communications (C3), etc.) are responsible for the mission deliverables.

PERFORMANCE WORK STATEMENT (PWS): The description of tasks or services to be performed and end products to be delivered by the Contractor. The PWS also defines facilities, property, and support to be provided to the Contractor by the Government.

PLANNING, PROGRAMMING, BUDGETING AND EXECUTION (PPBE): The development, integration, review, justification, validation, and management of budget development activities. A process generally conducted annually during the first quarter of each calendar year for the purpose of establishing budget profiles for the out-years.

PROGRAM: A strategic investment by a Mission Directorate (MD) or Mission Support Office that has a defined architecture, technical approach, requirements, funding level, and a management structure that initiates and directs one or more projects. A Program defines a strategic direction that the Agency has identified as critical.

PROGRAM MILESTONE: A designated point in flight or ground hardware development and processing, uniquely defined by each NASA Program, in which a set of critical objectives is planned or has been completed. The Program will conduct a review at a milestone event to ensure that all supporting elements are ready to proceed with activities to achieve the next milestone in the schedule.

PROGRAM PLAN: The document that establishes the Program’s baseline for implementation, signed by the MD Associate Administrator, Center Director(s), and Program Manager.

PROGRAMMATIC AND STRATEGIC INTEGRATION (PSI): One of the two entities that has authority, accountability, and responsibility for cross-Program integration. PSI provides programmatic integration, which includes integrated budget/schedule/content/risk management and assessment. PSI consists of members from ESD and the three (SLS, Orion, and EGS) Programs through multiple working groups.

PROGRAMMATIC CHANGE REQUESTS: See change requests.

PROJECT: A specific investment that has defined requirements, a life cycle cost, a beginning, and an end. A project yields new or revised products, services, or results in support of an EIT.

Each EIT may include multiple projects.

Page 16 of 18 Attachment J-17

Q

QUANTITATIVE RISK ANALYSIS: Risk analysis process which assigns a numeric value to the probability of loss based on known risks and available, objective data. Used to determine values such as potential impacts to cost and schedule.

R

RANGE PROGRAM REQUIREMENTS DOCUMENT: The customer’s request to the Range describing in detail the customer’s requirements for support of the program. It lists operation or test paramerters, reports, data reduction, analyses, and evaluation requirements.

REACH BACK: The capability to identify, acquire, and deliver a resource (skill set) from within the corporation’s workforce in order to accomplish a short or long-term support service for the EGS Program.

RECOVERY: Post-landing activities associated with returning spacecraft.

REFERENCE: Provided for background or information.

RELIABILITY: The probability that an item, system, subsystem, component, or part will perform the intended and required function under specified conditions at a designated time for a specified interval.

RESOURCE ENVIRONMENT FOR ENHANCED BUDGETING (REEB): An automated repository containing EGS budgets allowing ad-hoc queries and report writing.

REVIEW ITEM DISCREPANCY (RID): Comments submitted by reviewers during a Program Life-Cycle Review.

RISK: The probability, severity, and uncertainties that a program or project will experience an undesired event (some examples include a cost overrun, schedule slippage, malicious activities, environmental impact, failure to achieve a needed technological breakthrough or project success criteria) and the consequences, impact, or severity of the undesired event, were it to occur. Both the probability and consequences may have associated uncertainties.

RISK ASSESSMENT: An evaluation of a risk item that determines (1) what can go wrong, (2) how likely is it to occur, and (3) what the consequences are.

RISK MANAGEMENT: The process of balancing risk with cost, schedule, and other programmatic considerations. It is an organized, systematic decision-making process that efficiently identifies, analyzes, plans, tracks, controls, communicates, and documents risk to increase the likelihood of achieving program/project goals.

RISK REVIEW PANEL: A team that reviews issues with potential safety, technical, schedule, and cost risk, whose lead makes recommendations to the appropriate authority.

Page 17 of 18 Attachment J-17

S

SCHEDULE RISK ANALYSIS (SRA): A technique to connect the risk and uncertainty information of project activities to tasks in the schedule in order to assess probable risk informed durations of individual project activities and how they are linked to assess the likely final program duration.

SENSITIVE BUT UNCLASSIFIED (SBU): Information that may be Program sensitive, including ITAR or EAR, but does not contain any classified information. Examples of SBU information include ITAR, EAR, proprietary, limited rights, source selection, Program pre-decisional, proposal, Small Business Innovative Research, privacy act, national space policy prior to public release, and drawings and specifications of specific mission essential infrastructure.

SHAREPOINT: Web Application Collaborative environment utilized by the EGS Program.

SPACE LAUNCH SYSTEM (SLS) PROGRAM: The SLS Program, assigned to the Marshall Space Flight Center (MSFC), is responsible for developing a heavy-lift launch vehicle with sufficient capability to enable exploration beyond LEO and alternate means of transportation for crew and payload to the International Space Station (ISS) in case the primary mode of transportation is not available.

STAKEHOLDER: Program stakeholders are individuals or organizations who either benefit from the services and activities of the Program, provide resources to the Program, or have a financial or functional interest in Program activities. Stakeholders within the EGS Program include functional teams such as Ground Systems Implementation or Operations Flow Teams, and offices controlling funding for projects. NASA Stakeholders external to the Program include other Centers and NASA Headquarters (HQ), other Exploration Systems Development Programs, Agency management councils and panels, independent review boards, other organizations at KSC, KSC management councils, and the contractor workforce across the NASA Centers.

STANDARD OPERATING PROCEDURES (SOPs): Written procedural guides developed by the Contractor pertaining to contract performance.

STRATEGIC COMMUNICATION: An effort to develop a conceptual umbrella strategy for communicating programmatic content and function in different messaging platforms to ensure coherence to prevent contradictory, confusing messaging, to different groups across all media platforms.

SUBSYSTEM: A secondary or subordinate system within a system that performs a specific function or functions. Examples include electrical power, guidance and navigation, attitude control, telemetry, thermal control, propulsion, structures subsystems. A subsystem may consist of several components (hardware and software) and may include interconnection items such as cables or tubing and the support structure to which they are mounted.

SUPPLY CHAIN: The specific group of suppliers and their interrelationships that is necessary to design, develop, manufacture, launch, and service the program or project. This encompasses all levels within a space system, including providers of raw materials, components, subsystems, systems, systems integrators, and services.

Page 18 of 18 Attachment J-17

SYSTEM: The combination of elements that function together to produce the capability required to meet a need. The elements include all hardware, software, equipment, facilities, personnel, processes, and procedures needed for this purpose.

SYSTEMS ENGINEERING: A disciplined approach for the definition, implementation, integration, and operation of a system (product or service). The emphasis is on achieving stakeholder functional, physical, and operational performance requirements in the intended use environments over planned life within cost and schedule constraints. Systems engineering includes the engineering processes and technical management processes that consider the interface relationships across all elements of the system, other systems, or as a part of a larger system.

T

TECHDOC: A distributed, portable document management system designed for the management of any type of document or file. The system is web-based and provides for an electronic means to: Manage documents through their entire life cycle; Provide extensive per-document security and access controls; Provide revision control of approved documents, etc.

TECHNICAL INTERCHANGE MEETING (TIM): A meeting between two or more technical teams (to discuss designated technical issues, exchange information, develop processes, and/or work issues.

V

VALIDATION: The process of providing the objective evidence that a subsystem, system, or end item satisfies its intended use when placed in its intended environment.

VERIFICATION: The process of providing the objective evidence that a subsystem, system, or end item satisfies the design requirements and specifications.

W

WORK BREAKDOWN STRUCTURE (WBS): A product-oriented hierarchical division of the hardware, software, services, and data required to produce the Program/project's end product(s), structured according to the way the work will be performed, and reflective of the way in which Program/project costs, schedule, technical, and risk data are to be accumulated, summarized, and reported.

WORK YEAR EQUIVALENT (WYE): The total productive labor hours in a contract year that Contractor employee is available for work, excluding non-productive time (e.g., holidays and paid leave).

[END]

ATTACHMENT J-18

GOVERNMENT PROVIDED FACILITIES

Government Provided Facilities Attachment J-18

Area Facility Number

Acronym Title Shared with other Contractors

LC 39 K6-1096 OSBI Operations Support Building I Yes LC 39 K6-1249 OSBII Operations Support Building II Yes LC 39 K6-0900 LCC Launch Control Center Yes LC 39 J7-0689 Pad-B Pad-B Yes LC 39 TR5-0629 ML Mobile Launcher Yes

KSC Industrial M7-0508 LETF Launch Equipment Test Facility Yes

KSC Industrial M7-0355 O&C Neil Armstrong Operations &

Checkout Building Yes

Government Provided Facilities

Room numbers to be assigned by NASA during Phase-In.

Government Provided Facilities Attachment J-18

Cover Sheet

ATTACHMENT L-01

KEY POSITION MINIMUM QUALIFICATIONS TEMPLATE

[PAGE INTENTIONALLY LEFT BLANK]

Key Position Min Qual

Please add or delete pages as needed and adjust for printable area.

KEY POSITION MINIMUM QUALIFICATIONS

Government Labor Classification
(select from drop-down list)Offeror

Labor Classification Offeror Minimum Education Offeror Specific Skills

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

Experience level:

Description:

80KSC018R0006 KLXS III RFP Key Position Minimum Qualifications Attachment L-01

Page &P of &N

Gov Labor Class

Gov Labor Classification

1 Analyst I

2 Analyst II

3 Analyst III

4 Business Specialist I

5 Business Specialist II

6 Business Specialist III

7 Business Specialist IV

8 Cost Estimator/Analyst I

9 Cost Estimator/Analyst II

10 Cost Estimator/Analyst III

11 Engineer I

12 Engineer II

13 Engineer III

14 Engineer IV

15 Engineer V

16 Intern I

17 Intern II

18 IT Support Specialist I

19 IT Support Specialist II

20 IT Support Specialist III

21 Manager

22 Management Analyst I

23 Management Analyst II

24 Management Analyst III

25 Management Analyst IV

26 Program Manager

27 Schedule Analyst I

28 Schedule Analyst II

29 Schedule Analyst III

30 Schedule Analyst IV

31 Subject Matter Expert

80KSC018R0006 KLXS III RFP &A Attachment L-01

&A &P / &N

ATTACHMENT L-02

PAST PERFORMANCE QUESTIONNAIRE

Exploration Ground Systems (EGS) Program

Kennedy LX Support ContractThree (KLXS III)

John F. Kennedy Space Center, Florida

This questionnaire is submitted for your evaluation by a company that has intentions to compete for the KLXS III contract as a prime or major subcontractor. The following terms, “customer reference” and “evaluator,” are used to refer to the person performing the evaluation. For the KLXS III Request for Proposal (RFP), NASA requires the company to provide this questionnaire to customer references for which it has had an active or completed contract in the past three (3) years. Please complete this questionnaire and return to NASA per the following instructions. Your assistance in this effort is greatly appreciated.

The KLXS III contract is in support of the EGS mission goals as provided by Exploration Systems Development (ESD) and includes ground systems development and operational planning for launch vehicles, spacecraft, and payloads. The EGS Program is responsible for developing the infrastructure, equipment, and processes to conduct the integration, ground processing, and launch of the SLS launch vehicle and Orion spacecraft. KLXS III support for EGS ground systems development and operational planning crosses multiple projects and Programs including Space Launch System (SLS), and Orion.

The principal purpose of KLXS III is to provide Program level engineering and technical services, program and business management support services, and administrative support services to the EGS Program (organizational mail code LX). The scope of this contract includes supporting ground systems and space flight systems planning and design; project management and integration; operations integration and analysis; technical requirements development, management, and compliance; and cost, risk, configuration management, and schedule integration and analysis.

PAST PERFORMANCE QUESTIONNAIRE INSTRUCTIONS

Section I: Provide a description of the company and the contract for which you are a customer reference. If the work content element was not performed under the contract leave the evaluation row blank.

Section II: Provide your assessment of the company’s experience level and performance as evidenced within the contract for which you are a customer reference. It is very important to keep in mind that only experience on active or completed contracts in the last three (3) years is relevant.

Experience

Level Rating

Definition

Significant

Full range of services was routinely performed by the contractor for the applicable work content.

Moderate

Experience in several aspects of this area of work, even though the experience may not have been on a continuous basis.

Minimal

Although at least some aspects of the work content may have been performed, such performance was limited in scope or frequency.

Section III: Provide evaluation of the company’s performance. Additional pages may be used for comments if desired. It is very important to keep in mind that only performance in the past three (3) years is relevant.

Please use the following definitions to assess the company’s Performance Rating for Sections II and III:

Performance

Rating

Definition

Exceeded

Exemplary performance in a timely, efficient, and economical manner; very minor (if any) weaknesses with no adverse effect on overall performance.

Met

Met the established requirements. Effective performance; fully responsive to contract requirements; reportable weaknesses, but with little identifiable effect on overall performance.

Failed to Meet

Did not meet minimum acceptable standards in one or more areas; remedial action required in one or more areas; deficiencies in one or more areas which adversely affect overall performance.

Not Rated

Not Rated

Section IV: Provide evaluation of the company’s management of cost and award/incentive fee history.

Section V: Provide overall evaluation of the company.

Section VI: Provide information about you (the evaluator). The KLXS III Source Evaluation Board may contact you regarding the information you provide.

Please complete, sign and scan, this questionnaire and attach the file to an email addressed to the KLXS III Contracting Officer (KSC-KLXSIII-info@mail.nasa.gov) no later than 3:00 p.m. KSC local time, on May 16, 2018. If there are any questions, please contact the Contracting Officer, Karen Griffin, at (321) 867-6277.

Section I. Company and Contract Information

1. Contractor (Company/Division/Mailing Address):

2. Proposing as the |_| KLXS III Prime or as a |_| Subcontractor under KLXS III

3. If proposing as a KLXS III subcontractor, identify the KLXS III prime contractor associated with the KLXS III teaming arrangement:

4.

DUNS #

CAGE Code:

5.

Contract Number:

NAICS Code:

6.

Contract Type (e.g. FFP/CPAF/CPFF):

7. Contract Title/Short Description (provide the Contract title and a brief description of the services provided under this contract):

8. Description of how the respective contract is similar in size, content, and complexity to the KLXS III requirements. It is not sufficient to state it is comparable in magnitude and scope. Rationale must be provided to demonstrate how it is comparable.

9. Method of Acquisition: |_| Competitive |_| Sole Source

10. Average number of personnel on the contract per year:

11. Place of Performance:

12. Contract Award Date:

13. Planned Period of Performance (basic and any options):

14. Actual Contract Period of Performance:

15. During this contract, the contractor provided services as a:

Prime Contractor

|_| Major Sub-Contractor

Other (please describe)

16. If the primary role of the past performance was served in the capacity of a subcontractor, teaming arrangement, or Joint-Venture agreement, describe the specific portion of the scope performed under the contract. Also describe the percentage of the scope of work this entails.

If yes, please describe:

17. Does a corporate or ownership relationship exist between the contractor being evaluated and your organization? |_| Yes |_| No

If yes, please describe the relationship:

18. Unusual contract features or conditions:

Section II. Relevant Experience Level Rating and Peformance Rating

Note: NASA EGS “Ground Systems” are defined as Systems used to process or test flight hardware during ground processing; including unique facility systems; non-flight equipment, systems, or devices specifically designed and developed for a direct physical or functional interface with flight hardware; Infrastructure and equipment (portable or fixed) that provide functional and/or physical support to direct interface ground support equipment.

KLXS III Work Content

Experience Level Rating

Performance Rating

Significant

Moderate

Minimal

Exceeded

Met

Failed to Meet

Not Rated

1. GENERAL CONTRACT REQUIREMENTS

a. Contract Management and Administration

b. Contract Financial Management

c. Information Technology (IT) Management and IT Security: Includes compliance of applicable IT Security policies.

d. Safety and Health: Includes compliance of applicable Safety and Health policies.

e. Environmental Management: Includes compliance of applicable environmental policies.

f. Security Management: Includes compliance of applicable security policies.

2. PROGRAM MANAGEMENT

a. Program Control and Business Management: Includes financial analysis of ground systems projects and Program life cycle financial analysis.

b. Programmatic Integration and Analysis: Includes probabilistic risk analysis and developing program specific metrics.

c. Schedule Integration and Analysis: Includes developing, integrating, maintaining, and assessing Program and project level schedules to support Program planning, risk analysis, and decision-making activities. In addition, includes evaluating and identifying Program level critical path and schedule risks.

d. Strategic Communications Planning: Includes industry assessments and developing communications products. Also includes developing communications products and generating awareness of program goals for public engagement and outreach activities.

e. Risk Management: Includes identification, tracking, and mitigation of technical and programmatic risks.

f. Information and Configuration Management (ICM): Includes configuration control and accounting of programmatic documentation.

g. Programmatic and Strategic Integration (PSI): Includes planning, coordination, and development of EGS programmatic products to include integrated costs and budgets, integrated schedules and interdependencies, risk assessments, strategic communication activities, and Program Life Cycle milestone events.

h. Technical Reports, Documentation, and Presentations: Includes Technical writing, assisting in documenting and ensuring compliance with Government program/project management practices (e.g. NPR 7120.5), and Program External Audit representation.

i. Program Management Integration Support: Includes Development and integration of reporting products (e.g., technical, risk, schedule, and cost assessments) necessary for monthly Program management reviews.

j. Administrative Program Support: Includes support for Programmatic boards and panels to document agendas, track action items, and coordinate conference room video and audio communications.

k. Program Specific IT Support: Includes IT property maintenance, website and portal content maintenance, automated data management, software tool maintenance, and IT Security Program implementation.

3. LOGISTICS MANAGEMENT AND INTEGRATION

a. Logistics Management and Integration: Includes logistics management and integration for development activities, planning for future operations, and Programmatic training certification coordination.

4. SYSTEMS ENGINEERING AND INTEGRATION

a. Technical Integration: Includes technical requirements development, Program baseline maintenance, technical compliance, Cross-project technical integration, and technical assessments in support of processing…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.