NNJ16582596R_-_RPOC_IV_Draft_C _L _M.docx

SECTION C - DRAFT STATEMENT OF WORK

1.0 PROJECT OVERVIEW/SCOPE OF WORK

This Statement of Work (SOW) outlines the requirements to provide engineering support services (research, analysis, design, development, integration, verification, test, evaluation, and operations support) supporting Guidance, Navigation and Control (GN&C), system engineering, and RPOC initiatives. The Contractor shall provide engineering support in projects and technical areas such as those below in support of the NASA Johnson Space Center (JSC) and its external customers:

· INTERNATIONAL SPACE STATION (ISS) PROGRAM

· ORION PROGRAM AND RELATED EXPLORATION INITIATIVES

· TECHNOLOGY DEVELOPMENT, SUPPORT, AND RESEARCH

The scope of these tasks encompasses the program architecture definition, analysis and development, as well as the entire spacecraft definition and development process including requirements development, concept development, technology development, system design, system and vehicle evaluation, system and vehicle test, verification, integration and operations support. Examples of tasks to support these systems includes the development of analysis tools, including modeling of space vehicles, vehicle subsystems, dynamics, and environment in a high-fidelity simulation environment, and development of tools to support command and monitoring analysis including high fidelity graphics and user interfaces. The structure of the SOW should not be construed as defining a required organizational configuration. Specific tasks will be authorized on task orders.

NASA will provide facilities for vehicle software and other software required for the effort onsite at NASA JSC and make it available for use at the Contractor facility through a network server account.

Performance of the work under this contract is subject to the technical direction of the Contracting Officer’s Representative (COR), who shall be specifically appointed by the Contracting Officer (CO) in writing. "Technical direction" means a directive to the Contractor that approves approaches, solutions, designs, or refinements; fills in details or otherwise completes the general description of work or documentation items; shifts emphasis among work areas or tasks; or furnishes similar instruction to the Contractor. Technical direction includes requiring studies and pursuit of certain lines of inquiry regarding matters within the general tasks and requirements in Section C. Technical direction does not include authorizing contractual instruments.

Contractor personnel may be required to travel to participate in major reviews and technical interchange meetings for many of these tasks. This travel may be both domestic and international. Details of expected travel will be provided in task orders.

2.0 DESCRIPTION OF WORK

2.1 PROJECT MANAGEMENT

The Contractor shall be responsible for the management of the contract to assure accomplishment of contract work and compliance with contract clauses and Data Requirement Documents (DRDs). The Contractor shall provide all management, supervision, programming, technical, and administrative support, as well as technical disciplines, skills and documentation necessary to ensure effective and efficient accomplishment of the total contracted effort.

The Contractor shall assure that the project management team has the authority necessary to respond to appropriate contractual direction, is responsible for effort relating to technical and administrative functions, and will maintain a focal point for management of all contract data requirements and issues.

The Contractor’s project management shall ensure that there are single point interfaces with the NASA JSC CO and COR.

2.2 ISS PROGRAM

2.2.1 The Contractor shall support verification of ISS Visiting Vehicles using RPOC related ISS requirements. The analysis of the vehicles, trajectories, and operations includes simulation of the vehicle, the ISS, and the environment. The vehicles included in this effort deliver cargo and crew to the ISS. Visiting Vehicles operations concepts include both capture/berthing and self-docking vehicles. All non-Russian Visiting Vehicles will be assessed. The purpose of these analyses is to ensure each vehicle’s adherence to applicable ISS requirements and Commercial Crew Transportation Capability (CCtCAP) (when applicable) requirements.

For visiting vehicles in the design phase, the Contractor shall support an assessment of each vehicle’s design to verify that the design meets all applicable ISS and CCtCAP (when applicable) requirements during the ISS rendezvous, proximity operations, docking, undocking, and departure phases of flight. Work will include development of an independent GN&C simulation for each visiting vehicle, as well as, a review of vehicle design, development, certification, and mission specific products. The Contractor shall also support the development, test, and verification of the ISS crew monitoring capabilities to be used during the approach, capture or docking maneuver, docking, if applicable, undocking, and departure from the ISS.

The Contractor shall provide NASA with documentation and results to support a recommendation relative to certification of flight readiness (CoFR) for each non-Russian visiting vehicle and shall identify and record any limitations of the content and analysis supporting the recommendation.

2.2.2 The Contractor shall support development of simulation and analysis tools for each of the vehicles using the existing NASA/JSC simulation development environments. These software tools will be used to support independent vehicle design and development evaluations, mission design assessments, ISS requirements analysis and verification, and ISS and crew safety evaluations. Elements of this tool set shall be provided to the ISS Program for integration into the crew and flight controller training simulation tool sets.

2.3 ORION PROGRAM AND RELATED EXPLORATION INITIATIVES

2.3

2.3.1 The Contractor shall support NASA JSC’s efforts in GN&C areas related to the Orion Program and related exploration initiatives. This effort includes planning, designing, and developing software tools and simulation products to support mission design/evaluation, requirements analysis, strategy development, and safety evaluation. Software, software tools, and simulation products will be used to perform the requirements. This support may include the following–

· GN&C requirements development/assessment.

· Architecture, mission design, reference mission assessments, GN&C system level evaluation and assessment.

· GN&C technology assessments and evaluations.

· Use of software, software tools, and simulation products to conduct mission design/evaluation, requirements analysis and safety evaluation. Legacy software tools rely on the Trick and JSC Engineering Orbital Dynamics (JEOD) simulation environments.

· Hardware, integration, lab maintenance, and simulation development support.

· Integration of GN&C related flight software elements for delivery to the Orion prime Contractor.

2.4 TECHNOLOGY DEVELOPMENT, SUPPORT, AND RESEARCH

2.4

2.4.1 The Contractor shall provide specialized support for development, analysis or research of technologies related to NASA JSC activities. This support may include the following –

· Support development and use of software, software tools, and simulation to support GN&C technologies

· Provide specialized support for tool development and/or implementation in NASA/JSC’s development, analysis and test labs. Specialized support includes support unique to the tools and models, analysis, and hardware developed for the JSC activities outlined in Sections 2.2 and 2.3

· Support development of prototype tools as required to validate new concepts

· Support design and development of guidance and trajectory tools

· Support performance systems engineering and requirements development and analysis

· Support development of ground and on-orbit test and demonstrations designed to investigate and validate new technologies

· Leverage existing tools, processes and experience to minimize additional development and analysis effort

2.4.2 The Contractor shall support research and develop prototype GN&C concepts to support improvements in the ascent, rendezvous, on-orbit, entry, and landing phases of flight. These include related systems/subsystems and software to enhance failure detection, isolation, and recovery (FDIR), command and control, crew visualization and intervention and other vehicle or system/subsystem functions.

3.0 REPORTING REQUIREMENTS

Reporting shall adhere to requirements as defined in the Data Requirements List (DRL).

4.0 QUALITY ASSURANCE

JSC is Society of Automotive Engineers (SAE) AS9100 registered and intends to maintain this certification. The Contractor shall perform all work on-site in accordance with the JSC Quality Management System. Any work performed off-site, using the JSC network server, shall also comply with the JSC Quality Management System.

5.0 SAFETY AND HEALTH

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

6.0 REFERENCE DOCUMENTS

The following documents and schedules are applicable for the work to be performed under the Statement of Work:

1. SSP41000 System Specifications for International Space Station (ISS)

2. SSP41163 Russian Segment Specification

3. SSP50038 Computer Based Control System (CBCS) Requirements

4. SSP50021 ISS Safety Requirements Document

7. SSP50273 Segment Specification for the H2 Transfer Vehicle (HTV)

9. SSP50575 Bilateral H2 Transfer Vehicle (HTV) Operations Plan

10. NPR 8705.2 Human-Rating Requirements for Space Systems

11. SSP50808 International Space Station (ISS) To Commercial Orbital Transportation Services (COTS) Interface Requirements Document (IRD), Revision A

12. NPR 7150.2B NASA Software Engineering Requirements

13. JPR 7150.2 JSC Software Engineering Procedural Requirements

14. JPR 1280.2E Quality Manual

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The Offeror is cautioned that the listed provisions may include blocks that must be completed by the Offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the Offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this/these address(es):

http://www.acquisition.gov/far/ http://www.hq.nasa.gov/office/procurement/regs/nfstoc.htm

(END OF PROVISION)

NOTICE: The following contract provisions pertinent to this section are hereby incorporated by reference:

I. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

II. NASA FAR SUPPLEMENT (48 CFR CHAPTER 18) CLAUSES

(END OF PROVISION)

L.2 52.215-20 Requirements for Certified Cost or Pricing Data or Data other than Cost or Pricing Data (OCT 2010) – Alt. IV (OCT 2010)

(a) Submission of certified cost or pricing data is not required.

(b) Provide data described below: See Provision L.16.6, Volume III – Cost and Price Proposal

L.3 Type of Contract

The Government contemplates award of an Indefinite-Delivery, Indefinite-Quantity (IDIQ) contract with Cost-Plus-Fixed-Fee (CPFF) task orders resulting from this solicitation. The phase-in plan is Firm-Fixed-Price.

L.4 52.233-2 SERVICE OF PROTEST (SEP 2006)

(a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), shall be served on the Contracting Officer (addressed as follows) by obtaining written and dated acknowledgment of receipt from:

NASA Johnson Space Center, ATTN: BH4/Anna Carter 2101 NASA Parkway Houston, TX 77058 Phone: 281-483-1869 Fax: 281-483-4066 Email:Anna.Carter-1@nasa.gov

(b) The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO

L.5 52.252-5 AUTHORIZED DEVIATIONS IN PROVISIONS (Apr 1984)

(a) The use in this solicitation of any Federal Acquisition Regulation (48 CFR Chapter 1) provision with an authorized deviation is indicated by the addition of “(DEVIATION)” after the date of the provision.

(b) The use in this solicitation of any NASA FAR SUPPLEMENT (48 CFR CHAPTER 18) provision with an authorized deviation is indicated by the addition of “(DEVIATION)” after the name of the regulation.

(END OF PROVISION)

L.6 RESERVED

L.7 Proposal Marking and Delivery

(a) Methods of Proposal Delivery

Interested parties are required to submit offers, bids, or quotes electronically via the Federal Business Opportunities (FBO) system (www.fbo.gov). Proposals or quotes submitted using any other mechanism, such as U.S. Postal Service or Commercial Delivery Service will be deemed non-responsive.

(b) The following are requirements for the online FBO Electronic Proposal Response submission:

1) Vendors must login to the FBO system to submit proposals in response to a Request for Proposal (RFP)

2) Vendors must be registered in the System for Award Management (SAM) at www.sam.gov prior to submitting a proposal

3) Vendors must have a CAGE Code prior to registering in SAM For additional information on submitting electronic proposal responses via the FBO system see the FBO Vendor Guide Section 4.3.1 Submitting an Electronic Response (https://www.fbo.gov/downloads/FBO_Vendor_Guide.pdf).

(c) Note to Offerors:

The FBO website has a 10 MB maximum capacity for each file upload. Given the volume of data and information to be submitted by Offerors in response to a solicitation, and the inherent limitations of internet bandwidth, Offerors may be required to submit sections in multiple uploads. Offerors shall label multiple uploads by naming each file as the following example, Volume 1 Technical 1 of 3. It is critical that Offerors carefully and completely identify all parts and attachments of the proposal.

Consider the file size and number of files to be uploaded when submitting your proposal in FBO.

Proposals are considered to be timely when the entire proposal is uploaded into FBO by the date and time stated in the SF33. In accordance with FAR 15.208, if the proposal/quote was not received at the initial point of entry to the Government infrastructure (in this case, received through FBO) by the exact date and time specified on the cover page of this solicitation, it will be determined late. Proposal/quote is defined to mean ALL volumes or parts required in the solicitation are included in the electronic submission.

Note: There is no "expected" or "target" length of time for proposal submission; size and content may be factors, therefore Offerors are strongly cautioned when submitting proposals to allow adequate time for submission.

Solicitations may remain posted on the FBO after the solicitation closing date. If the response deadline has passed for the solicitation, vendors will no longer be able to submit proposals.

(d) Any award issued as a result of this solicitation will be distributed electronically.

(e) Questions pertaining to this solicitation should be directed to the Contracting Officer identified in Block 10 on the cover page of this solicitation.

(END OF PROVISION)

L.8 52.242-90 JSC Super-Flex Work Schedule (MAR 2014) (JSC Procurement Instruction)

Through Super-flex, JSC civil servants are encouraged to utilize the current civil service schedule to work 80 hours in a pay period, while “flexing” every other Friday simultaneously with the Center (first Friday of the JSC pay period). These Fridays are called “Flex Fridays”. Super-flex also expands the use of Work from Anywhere (WFA)/telework.

JSC does not require that our Contractor team members adopt a matching schedule. However, Offerors should be aware that many civil servant customers will not be onsite on “Flex Fridays” and the Center will go in “weekend mode” on “Flex Fridays”. "Flex Friday weekend mode" provides exceptions for some buildings. For more information on "Flex Friday weekend mode" and Super-flex, reference http://procurement.jsc.nasa.gov/docs/Super-Flex Phase 2.docx

(END OF PROVISION)

L.9 Availability of Specifications

(a) For the purpose of this RFP, the Technical Reference Library contains the official versions of applicable and reference documentation. No other version of the documentation should be used.

(b) All technical documentation which is incorporated directly by reference in this solicitation may be obtained from the RPOC IV Technical Reference Library which is available online at the following url:

[http://procurement.jsc.nasa.gov/rpoc/]

(c) In order to obtain a User-ID and password to access the documents above, please e-mail the following information to the Contract Specialist at colleen.l.wells@nasa.gov:

(d) All copy-righted technical documentation which is incorporated directly by reference in this solicitation cannot be placed on the RPOC IV Technical Reference Library. If the Offeror desires to have these copy-righted documents to prepare their proposal they must be obtained, at the bidder's expense, from the organization that develops, establishes and/or publishes those documents.

(e) Upon request, the Contracting Officer will furnish to the Offeror NASA technical documents not incorporated by reference.

(END OF PROVISION)

L.10 Communications Regarding This Solicitation

Any communications in reference to this solicitation shall cite the solicitation number and be directed to the following Government representatives:

QUESTIONS REGARDING THIS SOLICITATION MUST BE PRESENTED IN WRITING and shall be submitted electronically to both of the above e-mail addresses by [Date TBD] in order that answers may be obtained and disseminated in a timely manner, since it is not expected that a proposal submission date will be extended. Oral communications are not acceptable in response to this solicitation. Questions shall not be directed to the technical activity personnel.

(END OF PROVISION)

L.11 Offeror Acceptance Period

Proposals submitted in response to this solicitation shall remain firm for at least 180 calendar days after the date specified for receipt by the Government and shall contain a statement to this effect.

(END OF PROVISION)

L.12 Period Covered by Procurement

This solicitation covers a period of a 45-day Phase-In and a five (5) year period of performance. For contracting purposes:

(END OF PROVISION)

L.13 Instructions for Proposal Preparation

This section provides detailed instructions to Offerors to be used in the preparation of proposals. It is organized as follows:

L.13.1 Introduction

This acquisition is being conducted as a competitive, Total Small Business Administration set-aside. In providing these instructions, the Government’s intention is to solicit information that will permit a competitive evaluation of the Offeror’s proposal. The information solicited will demonstrate the Offeror’s competence and capability to successfully complete the requirements specified in the RPOC IV SOW. Generally, the proposal shall:

Table L-1 Cross Reference from Section L to Section M

L.13.2 PROPOSAL Arrangement, Page Limitations, Copies, and Due Dates

(a) The entire proposal is due by the date stated Table L-2. The delivery location is specified in L.8, Proposal Marking and Delivery. Late proposals will not be accepted in accordance with FAR 52.215-1, “Instructions to Offerors – Competitive Acquisition.”

(b) Proposal Arrangement: Offerors shall arrange their proposals as set forth below in Table L-2. Proposal sections excluded from the page limit shall be placed at the end of each volume.

Table L-2: Overview of Proposal Volumes, Page Limitations, Copies, and Format

The following requirements apply to the sections of the proposal which are page limited:

Sections of the proposal which are page limited shall be prepared and submitted using non-compressed Arial font with single-spaced 12 point text with a one-inch margin on all sides in accordance with Microsoft Word default settings. Character spacing shall be “Normal” per Microsoft Word settings. Text in diagrams, charts, tables, artwork, and photographs shall be no smaller than 12 point text size. Diagrams, charts, tables, artwork and photographs shall not be used to circumvent the text size limitations of the proposal. The margins may contain headers and footers but shall not contain any proposal content to be evaluated.

All pages in each volume shall be numbered sequentially with Arabic numerals (1, 2, 3, etc.) for contents subject to page limitations. Each side of the sheet, tab, or divider containing proposal material will be counted as part of the appropriate volume’s page limitations. Information that can be construed as belonging in another volume of the proposal will be so construed and counted against the appropriate volume’s page limitation.

Title pages, table of contents, cross-reference matrices, glossaries, acronym lists, page tabs, and section dividers that do not contain information that can be construed as proposal information will not be counted as part of the page limitations. However, these pages shall be numbered with lower case Roman numerals (i, ii, iii, etc.) in order to provide ease of reference for the Government.

Pages submitted in excess of the limitations specified in this provision will not be evaluated by the Government and will be returned to the Offeror in accordance with NFS 1815.204-70(b). Minor informalities or irregularities in a proposal that can be adjusted, corrected, or waived without being prejudicial to other Offerors may be accepted if it is immaterial to the acquisition. However, any pages contained in a page limited section of your proposal which do not comply with the RFP requirements may be returned by the Government and not evaluated.

The following requirements apply to the sections of the proposal which are not subject to page limitations: Sections of the proposal which are not page limited do not need to abide by the font, size or margin requirements of the page limited sections, though the Offeror should ensure readability. All pages in each section shall be numbered sequentially with Arabic numerals (1, 2, 3, etc.). Title pages, table of contents, cross-reference matrices, glossaries, acronym lists, etc. shall be numbered with lower case Roman numerals (i, ii, iii, etc.) in order to provide ease of reference for the Government.

(END OF PROVISION)

L.13.3 52.215-112 STREAMLINED Procurement Proposal INSTRUCTIONS (Performance Price [Limited] Tradeoff (PPT) Proposal Instructions (FEB 2014) (JSC Procurement Instruction)

This procurement will be conducted using a combination of technically acceptable baseline requirements (Acceptable/Unacceptable) and tradeoff of past performance, and cost/price. The Government seeks to select an Offeror whose proposal represents the best value after evaluation (see provision M.2, Performance Price Tradeoff (PPT) Proposal Evaluation, for evaluation procedures). The baseline requirements are considered basic Government needs in determining technical acceptability.

Technical acceptability, past performance, cost/price, and other proposal requirements are discussed in detail below.

L.13.4 Technical Acceptability Factor - Volume I

The proposal must demonstrate that the offered services meet the requirements as set forth below. The Offeror shall describe or provide the following in Volume I:

SUBFACTOR A: MANAGEMENT APPROACH

The Offeror shall provide a management approach which discusses Paragraph C, Number 1-7 of the Management and Staffing Plan, Section J-[TBD] DRD[TBD].

NOTE: The compensation templates required to be submitted in Volume III, Section L.13.6, will serve as supporting data in the evaluation of both Volume III and the above Management and Staffing Plan.

SUBFACTOR B: TECHNICAL APPROACH

The Offeror shall provide a Technical Approach which discusses the plan to accomplish the scenarios detailed in Attachment L-4. Formulate a plan and submit a response for each scenario. Each response shall include discussions of:

· The activities to be performed and computer software required

· The significant interactions or data sharing among the applicable scenario functions

· The assumptions regarding the factors that drive the staffing or schedule needs for each of the labor categories

· A staffing profile for each of the functions outlined in each scenario and the skill levels of the resources proposed. The resources are to be correlated with the standard labor categories specified in Section B of this RFP

The Offeror should not include travel, office facilities or workstations in your response to the scenarios. Describe items of other direct costs needed to perform this task.

The Offeror is to assume that adequate processes and software for each system are already in place.

L.13.5 Past Performance - Volume II

(a) Provide information from organizations and companies for which your company has previously performed work, in order for the Government to obtain appraisals of past performance. Offerors, including joint ventures, major subcontractors (subcontracts with an estimated average annual value equal to or greater than $500,000.00) and the proposed program manager shall each provide information on no more than five (5) past contracts (subject to the page limitation constraints). References with Government contracts are preferred, but not required. Offerors with no past performance experience shall so state.

(b) Offerors shall consider the recency and relevance, as they relate specifically to this solicitation. Only contract period of performances within 3 years from the date of issuance of the RPOC IV original solicitation will be considered in the past performance evaluation.

(c) The following information shall be provided:

· Contract number, CAGE code, NAICS code, and DUNS number (if other than the prime, provide the prime’s contract number and the Offeror’s CAGE code and DUNS number)

· Contract value (If other than the prime, provide the overall contract value and the subcontract contract value)

· Number of full-time equivalent employees assigned to the contract (if other than the prime, provide the number of full-time equivalent provided by the applicable subcontractor/entity)

· Employing Agency/Company Name

· Point of Contact (including address, telephone and fax numbers, and e-mail addresses)

· If a Government Agency, include both the Contracting Officer and Contracting Officer’s Representative points of contact

· Contract Description

· Place of Performance

· Period of Performance

· Contract Type

· Status of Contract (current, terminated (if so, why), successfully completed (include completion date))

· Consent Letters executed by each subcontractor, teaming partner, proposed program manager and/or joint venture partner, authorizing the release of past performance information so the Offeror can respond to such information. See sample consent letter at Attachment L-1: Sample Consent Letter

Submit information on contracts that you consider relevant in demonstrating your ability to perform the proposed effort. The submission shall include rationale supporting your assertion of relevance. This submission shall clearly detail what portions of the Statement of Work, the prime, major subcontractors, proposed program manager, teaming partner, and/or joint venture partner are responsible for and the specific resources (workforce, management, facilities, or other resources) to be employed and relied upon to perform the proposed effort. If the Past Performance volume includes data on any affiliated company, division(s), business units, segments, or other organizations of your company, then provide a narrative to address what they will be responsible for and/or proposing to do and the specific resources (workforce, management, facilities, or other resources) to be employed and relied upon, such that said parent et al will have meaningful involvement in contract performance.

Complete the matrix in Attachment L-2 Past Performance Information as part of your response. In the event of a conflict between the narrative and the relevance matrix, the narrative will take precedence as the Offeror’s intended response.

Provide an organizational chart displaying the relationships between the parent company, affiliate, and/or any other organizational entity (division(s), business units, or other segments of your company) which are proposed to perform the effort.

(d) In addition to the information above, Offerors, any major subcontractors, as defined above, the proposed program manager, and any other organizational entity (parent or affiliated company, division(s), business units, or segments of your company, which is considered to provide meaningful involvement in contract performance, shall each submit the past performance questionnaire, Attachment L-3, to all of the point of contact references required in paragraph (c) above. The Offeror is responsible for ensuring that all references are directed to return each questionnaire by e-mail directly to the contact listed in the questionnaire.

Where an Offeror chooses to request, from a civil servant employee at JSC, that a past performance questionnaire be submitted on its behalf for its proposed key personnel, please be advised that a Limited Communications Notice (LCN) has been issued in conjunction with this solicitation. The LCN directs that all civil service personnel at JSC shall refrain from communicating with industry on any matters related to this competitive procurement; as a result, while the civil servants may respond to the past performance questionnaire they will be unable to provide status to the Offeror, or communicate in any other fashion with the Offeror, about that past performance request.

(e) You may include up to one (1) page of introductory material about the experience and performance of your company and subcontractors (if applicable). This introductory material is in addition to the page limitation constraints. You may also submit additional reference information on experience and past performance for consideration. This additional information shall be subject to the page limitation constraints.

(f) Offerors shall provide the following performance data with explanatory remarks on contracts performed in the last three (3) years. Offerors shall identify the applicable North American Industrial Classification System (NAICS) Code for each contract and shall include points of contact for each contract. If a joint venture or prime-subcontractor relationship is proposed, the same information shall be provided for each company proposed. Explanatory statements shall be included as appropriate.

For all work performed during the past three (3) years, Offerors shall provide the following:

Environmental Data:

(1) Copies of any and all environmental non-compliance correspondence and citations from federal, state or local agencies or authorities with explanatory remarks.

Safety and Health Data:

(1) Copies of any and all OSHA citations with explanatory remarks.

(2) Records of the company’s occupational injuries and illnesses. These records shall include, for each worksite, as a minimum, number of occupational injuries and illness, annual average number of employees at the worksite, total hours worked by all employees, and applicable NAICS code. Provide records for the past three (3) years with signature of a company executive. Provide explanatory remarks of adverse performance and methods being used to improve performance. A copy of each year’s OSHA logs (Forms 300 and 300A) may be submitted or equivalent occupational injury and illness data.

(3) A letter from the insurance carrier providing workers’ compensation coverage (or equivalent) summarizing the Offeror’s Experience Modification Rates, loss run data, liability and lawsuit history related to safety and health performance for the past three (3) years including history of changes to the Experience Modified Rate. If an Offeror self-insures, provide and certify the same information (except the Experience Modification Rate history) with the signature of the responsible corporate officer or official.

(END OF PROVISION)

L.13.6 COST/PRICE PROPOSAL (Volume III)

Instructions for the preparation of the Cost/Price Proposal are organized as shown in the following Table and are presented below.

L .13.6 Paragraph Cost/Price Proposal Instruction Topic

(a)

Introduction

(b)

Specific Guidelines

Direct Labor Rates

Direct Labor Rate Escalation

Indirect Rate Historical Data and Analysis

Uncompensated Overtime

Standard Labor Categories

Model Contract Rates versus Cost Proposal Rates

(c)

Supplemental Cost Data

Financial Accounting Standard (FAS) 13 Analysis

Cost of Money for Facilities Capital

Fee

(d)

Pricing Methodology

Pricing for IDIQ RFP Specified Level of Resources

(e)

Excel Pricing Model (EPM) Introduction

(a) Introduction

The Offeror’s cost proposal shall be compliant with and based upon the Offeror’s estimating, accounting, and other applicable business systems. Certified cost and pricing data is not required; however, data other than certified cost and pricing data is required.

To ensure that the Government is able to perform a fair assessment of the proposed cost, the prime Offeror and all “major subcontractors” are required to submit a cost proposal that is suitable for evaluation. For the purposes of this solicitation, a “major subcontractor” is any team member (e.g., a subcontractor or inter-divisional organization) with an estimated average annual value equal to or greater than $500,000.00 over the period of performance for this contract as defined in Section L.12 PERIOD COVERED BY PROCUREMENT. A “minor subcontractor” is any team member (e.g., a subcontractor or inter-divisional organization) with an estimated total contract value below $500,000.00 over the period of performance for this contract as defined in Section L.12 PERIOD COVERED BY PROCUREMENT.

A cost proposal that is suitable for evaluation shall:

· Account for all resources necessary to complete requirements of this RFP.

· Provide traceability to the technical/management proposal(s).

· Explain in detail all pricing and estimating techniques.

· Disclose the basis of all projections, rates, ratios, percentages, and factors in sufficient detail to facilitate the SLPT’s understanding and ability to mathematically verify these estimating tools.

· Comply with applicable Federal Acquisition Regulation (FAR), NASA FAR Supplement (NFS), and statutory requirements.

· Include a discussion that explains all judgmental elements of cost projections and fee policies.

· Include all templates required in this RFP.

The Offeror’s cost proposal shall be submitted in one volume labeled Volume III Cost/Price Proposal. This Volume contains:

· A narrative which includes Sections (b) Specific Guidelines and (c) Supplemental Cost Data.

· The automated EPM workbook.

(b) Specific Guidelines

The following cost instructions apply to the prime Offeror and all “major subcontractors”:

1. Direct Labor Rates

For any direct labor rates not included in a Forward Pricing Rate Agreement (FPRA), the Offeror shall indicate the basis and/or source data (e.g., actual salary data as of a specific date, proposed salary data from a specific source as of a specific date, etc.) of any direct labor rate proposed. Indicate any adjustments that were made to the source data in order to derive the direct labor rates proposed in the initial contract year. If an adjustment(s) to the source data was made, indicate the reason(s) and rationale for the adjustment(s).

Note: If the Offeror’s proposed direct labor rates are based on information obtained from a third party salary survey/service provider, then the Offeror shall include the source data as part of their cost/price proposal.

2. Direct Labor Rate Escalation

For any direct labor rates not included in a FPRA, the Offeror shall provide the company's direct labor escalation history for the past three (3) years. The Offeror shall indicate the reason(s) for the historical escalation history. Further, the Offeror shall specifically provide, and explain, the rationale for any proposed direct labor rate of escalation going forward, whether positive, zero, or negative. Finally, if the historical rate of escalation is different than the proposed rate of escalation going forward, provide and explain the reason(s) why.

Note: The proposed direct labor rate of escalation discussed in this paragraph shall match the direct labor rate of escalation proposed in the EPM Total Compensation Templates (i.e.,TC(a) and TC(b)).

3. Indirect Rate Historical Data and Analysis

For any indirect rate(s) not included in a FPRA, the Offeror shall provide the company's indirect rate history for the past three (3) years. Further, the Offeror shall specifically provide, and explain, the rationale for any elements of cost in either the “pool” or the “base” that are driving significant changes in the indirect rate(s) going forward or that have resulted in significant changes to the indirect rate(s) versus the historical indirect rate data. Likewise, the Offeror shall indicate the primary reason(s) for any significant change in the indirect rate from one year to another year.

Note: Where an Offeror does not have three (3) prior years of history for an indirect rate, then that Offeror shall provide and explain both the basis of estimate and the rationale for the “pool” and “base” costs that comprise each indirect rate. Emphasis should be placed on the large and/or significant dollar items, but shall encompass no less than 75% of the total proposed “pool” and “base” items.

4. Uncompensated Overtime

The Government does not require the use of uncompensated overtime; however, if proposed, include a detailed narrative basis of estimate explaining your proposed methodology and provide your historical experience for similar work.

5. Standard Labor Categories

Standard Labor Categories (SLCs) to facilitate a consistent evaluation among Offerors are provided in Attachment L-6. Offerors shall map their labor categories to the SLCs. Offerors shall provide a brief narrative description of their labor categories and how they map to the SLCs to permit for a Government review based on the Offeror’s estimating system. Offerors are allowed to include additional SLCs for work that does not easily map into the SLCs provided in the solicitation. However, Offerors shall provide descriptions similar to the guidelines used in Attachment L-6 for SLCs.

6. Model Contract Rates versus Cost Proposal Rates

The Fully Burdened Rates (FBR) per SLC used in the development of the Offeror’s cost proposal shall match exactly with the FBR per SLC proposed in Section B.[TBD] of the Model Contract.

(c) Supplemental Cost Data

The following supplemental cost data, where appropriate, shall be submitted with the Cost/Price Proposal:

1. Financial Accounting Standard (FAS) 13 Analysis

If an Offeror is proposing to lease off-site facilities in order to perform this effort, the Offeror shall perform a FAS 13 analysis, as required by FAR 31.205-36 and FAR 31.205-11, in determining the classification of a lease as operating or capital. The Offeror is further reminded that this solicitation covers a 45 day phase-in period and a period of performance of 5 years (72 months).

The Offeror shall submit copies of any proposed lease, along with a statement of whether it considers the lease to be capital or operating, for purposes of reimbursement under the Contract. Regardless of whether the Offeror considers the lease to be operating or capital, the Offeror shall submit the rationale, with sufficient substantiation, to enable the Government to conclude that the Offeror’s categorization and proposed cost of the lease is correct. The Offeror shall indicate where these costs are included in the cost proposal elements. The Offeror should also include an analysis detailing the cost impact of treating the lease as an operating lease and the cost impact of treating the lease as a capital lease. Finally, the Offeror should discuss the significance of the impact of fluctuating Task Orders issued as a result of this IDIQ contract relative to the proposed lease and/or lease cost and how the Offeror would mitigate the cost impact upon on Government, if possible.

2. Cost of Money for Facilities Capital

The Offeror may choose to include the cost of money for facilities capital as authorized by Cost Accounting Standard (CAS) 414 and FAR 31.205-10 in the proposal. In the event the Offeror does not propose cost of money for facilities capital, FAR clause 52.215-17, “Waiver of Facilities Capital Cost of Money” shall be included in the Model Contract.

3. Fee

Include a discussion of how the proposed Not-To-Exceed (NTE) fee rate was derived and why it is reasonable for the type of effort. If a fee pool sharing arrangement is proposed, include a discussion of the arrangement and the distribution of fee earned.

(d) Pricing Methodology

For purposes of this solicitation, Offerors shall be required to provide their estimate of the required level of resources necessary to perform the SOW as discussed in the following paragraphs:

1. Pricing for IDIQ RFP Specified Level of Resources Offerors are required to develop a Contractor team composite FBR per SLC, per contract year, and then apply those rates to the respective hours provided in Table L -3. This pricing approach is facilitated through the Government-provided cost templates in the Excel Pricing Model, which is explained in detail in Paragraph (e) below.

Because of the uncertainties involved with IDIQ work, Offerors are cautioned that this estimate is not a guarantee of future work. Offerors are directed to Section B.[TBD] regarding the guaranteed minimum order for IDIQ.

Table L-3

NASA (JSC)

RFP Standard Labor Category

Contract Year 1 05/17-05/18 Contract Year 2 05/18-05/19 Contract Year 3 05/19-05/20

Contract Year 4 05/20-05/21

Contract Year 5 05/21-05/22

(e) Introduction EPM:

The goal of the EPM automated workbook is to provide a comprehensive working model of the Offeror’s proposed cost volume in an automated format. The pricing model shall be designed to facilitate changes to source data such as direct labor hours and/or rates, overhead and General and Administrative (G&A) rates etc. and be sophisticated enough to compute the total impact of various changes to both cost and price. It is important that your model facilitate this process to ensure fidelity and is error free. The cost proposal templates are designed to provide NASA with information necessary to perform a cost realism analysis.

The EPM is Attachment L-5. The requirements and instructions for inputting data into the spreadsheets are located either as a separate tab (e.g., FBR has an instruction tab and a tab to insert data) or within the individual tabs.

L.13.7 Responsibility…