SSPEDI_SpS_QandA_Vol3_7DEC2017.pdf

80ARC018R0007 December 7, 2017

Small Spacecraft Prototyping Engineering Development & Integration (SSPEDI) Space Solutions (SpS)

Questions and Answers, 7 December 2017

This document contains answers to questions regarding the SSPEDI SpS procurement that were received after the November 3, 2017 release of the final Request for Proposals (RFP).

Request for Proposals (RFP)

1. Q: Resource Workbook Attachment 5 states CLIN 2 effort includes WBS 1.6.1 and

1.6.2 which is prelaunch ground segment development and ops readiness, both of which are prelaunch efforts. In addition, ORS-8 SOW 3.6.1, 3.6.2 reference pre-launch development and operational readiness activities. We assume these pre-launch activities should be priced in CLIN 1 under WBS 1.3.2. Please confirm.

A: Yes, CLIN 1 includes pre-launch activities. The Resource Workbook (Attachment 5) has been modified to eliminate the inconsistency.

2. Q: The Attachment 4, Cost Price Template Workbook, explicitly worksheets 3a-f reference GFY Cost Summaries for Sub-tier subcontracts (e.g. rows 29 to 30), Since GFY pricing is not anywhere else within Section L, suggest sub-tier costs be reported only for task order years, as outlined in the Workbook.

A: Section J, Paragraph (b), Attachment 4, Cost Price Template Workbook is revised to remove reference to GFY.

3. Q: The RFP states that “For cost/price proposal purposes, major subcontractors are defined as those subcontractors providing a total value of $2,000,000 or more for the total task order period of performance, including all options.”

Does the Government anticipate to receive unsanitized proposals from major subcontractors (>$2,000,000) if the major subcontractors only provided sanitized proposals to the prime? If yes, what is the POC information that the major subcontractors will need to submit their proposals?

A: Yes, RFP Section L is amended to include the instruction for subcontractors to provide their full cost data directly to the Government if they wish.

4. Q: Note that the ORS-8 TRL-MRL Definitions pdf document is not readable. It appears there was a bad translation from a previous pdf file ("i" and "l"s are missing). Can you please repair/replace the file?

A: A revised document correcting the formatting issues is uploaded as an amendment to the RFP.

80ARC018R0007 Solicitation Questions and Answers December 7, 2017

5. Q: Are international subcontractors permitted on TO2 or the IDIQ contract in general? Are there export control restrictions on the SSPEDI RFP documents?

A: In general, international subcontractors are permitted as long as they are proposed within the restrictions provided in the RFP clauses and security requirements of each specific task order. There are no specific export control restrictions on the SSPEDI RFP documents but there are distribution limitations on some of the documents as provided on the front page of the applicable documents. For instance, the ORS-8 SOW requires special approval for distribution to any foreign entity. Offerors who access these documents shall adhere to the distribution restrictions.

6. Q: Will the USG consider adding FAR 252.219-7004 Small Business Subcontracting Plan (Test Program) to allow a contractor to use its comprehensive small business subcontracting plan?

A: The Government will not incorporate the DFARS Small Business clauses. The offerors shall submit a plan consistent with the requirements in Section L and

FAR 52.219-9.

7. Q: Per the RFP, the contractor is required to protect classified information and provide staff up to the Top Secret/Secret Compartment Information (TS/SCI).

The T.O. 2 DD254 (Attachment 4) does not have box e(1) SCI checked as "Yes."

Can you clarify?

A: While the basic IDIQ contract requires the ability to provide staff and/or facilities that meet TS/SCI level requirements, each task order may have its own classification based on the requirement. Task Order 2 ORS-8 Space Segment’s classification requirement is at the Secret level because some aspects of the work may be classified at the Secret level during performance. The DD254 has been issued to ensure that the contractor has the required capability.

8. Q: How will USG conduct a cost realism analysis to assess the reasonableness and realism of the proposed cost?

A: As indicated in the Cost/Price Volume in Section M.3(c)(2), Offerors should refer to FAR 2.101(b) for a definition of “cost realism” and to FAR 15.404-1(d) for a discussion of “cost realism analysis” and “probable cost”.

9. Q: Arial 12 font size is defined for all text, Arial 10 font size is defined for all "diagrams, charts, photographs". What is the font size limitation for table text?

Recommendation: Tables are typically classified in the same class as diagrams, charts, and photographs. Recommend Arial 10 font size for table text.

A: The instructions are correct. Tables should be formatted with 12 point font.

10. Q: Please confirm Building N244 ROOM 218 can accept and provide delivery receipts for physical deliveries of the proposal. If it cannot, can you please provide an alternate location that can accept delivery?

A: The RFP has been amended to change the location for “hand carried” delivery of proposals.

11. Q: Is the $2M threshold for a Major Subcontractor for a single subcontract or cumulative amount of all orders let to the same subcontractor?

A: The $2M threshold for a Major Subcontractor refers to the cumulative value of all proposed task orders (TO1 & TO2).

12. Q: Can definition be provided to the work associated with CLIN 003 and CLIN 004.

A: The work associated with CLINs 003 and 004 would fall under WBS 1.6, Mission Operations. See ORS-8 Space Segment SOW Sections 3.6.3, 3.6.4, and 3.6.5.

13. Q: The RFP states the contractor will receive Government Furnished Computer Software (GFCS). Will the ORS-8 GFP table be revised to reflect all the GFCS that the Government intends to provide?

A: GFCS will be identified on each applicable Task Order. Task Order 1 and Task Order 2 do not include GFCS.

14. Q: Are suppliers required to provide certified cost and pricing data?

A: In accordance with FAR 52.215-20, submission of certified cost or pricing data is not required in response to this RFP.

15. Q: RFP Section L.2(b) paragraph 15 refers to the following Section: "In accordance with NFS 1852.234-1 Notice of Earned Value Management System (EVMS), included in Section??..." Can the Government clarify?

A: Section L is updated in Amendment P00001to include the intended section of the EVMS clause.

16. Q: Given the short turnaround of this proposal, offerors may be unable to obtain proposals from subcontractors, and will instead rely on historical pricing from similar programs to price the proposal.

A: Offerors shall propose the estimated costs based on the instructions in section L and in accordance with the offerors’ approved accounting system.

17. Q: On RPF page L-14, section 1c refers to, "processes to protect classified information and provide staff at the various levels of clearance up to Top Secret/Special Compartment Information (TS/SCI)", and to "describe [the] approach to have a facility clearance and the capability to safeguard information, at the Top Secret level".

Can the Government provide a copy of the governing Security Classification Guide (SCG) to address these requirements, and can you clarify level of safeguarding required (TS vs TS/SCI)?

A: The SCG will be provided after contract award. The Government has determined that these documents are not necessary in order to respond to the

RFP.

18. Q: Are classified annexes to the proposal allowed? If so, is SCI allowed? If so, please provide submission instructions for classified annexes to the proposal.

A: No. It is the offeror's responsibility to ensure that all submitted proposal information is unclassified.

19. Q: The DD254 only provides guidance for FOUO information. Are there any other higher-level security classifications requirements on the current two (2) Task Orders?

A: See the answer to Question #7.

Model Task Orders

20. Q: In RFP Section B.2, is the "standard performance level" for each TRD requirement listed in the table at (2) of this clause to be interpreted as the requirement identified in each TRD requirement or some other value (e.g., the value identified as non-compliant)?

How will the values to be listed in the table at (4) of this clause be determined?

For instance, will those values be the performance value proposed by the offeror in those cases where the offeror proposes improved performance for the parameter?

How will the values to be listed in the table at (6) of this clause be determined?

For instance, will those values be the value identified as non-compliant?

A: The values listed in table at (2) will be based on the offerors proposed solution.

The same values will be identified in the table at (4) with a positive incentive earned when all of the proposed parameters are met within the required timeframe.

The same values will be listed in the table at (6) with a negative incentive earned when any of the proposed parameters are not met within the required timeframe.

21. Q: Would the government be open to granting an offeror the use of commerciality clauses?

A: The SSPEDI SpS is considered a non-commercial requirement and commercial clauses will not be used to establish the basic contract. The solicitation and resulting contracts contain FAR 52.244-6 Subcontracts for Commercial Items which provides the clauses for incorporation into subcontracts for commercial items.

22. Q: Can you confirm if SSPEDI TO 1/TO 2 will be either DPAS rated contract? If so, will it be DO or DX rated?

A: SSPEDI SpS TO 1 and TO 2 do not have a DPAS rating.

23. Q: Please provide copies of the Security Classification Guide (SCG), Program Protection Plan (PPP), and Operations Security (OPSEC) Guide.

A: These documents will be provided after contract award. The Government has determined that these documents are not necessary in order to respond to the

RFP.

24. Q: Please confirm if DoD SECRET in block 1a and b of the DD254 is correct.

A: Yes, it is correct.

25. Q: Please provide the detailed requirements specified in the following statement shown in DD254 block 14, “ensuring subcontractors are knowledgeable of and comply with the applicable requirements.”

A: The requirements refer to the VGSA as mentioned in Block 14 of the form.

26. Q: The Model Task Order 1 states that "The Government will evaluate equally, as regards time of delivery, offers that propose delivery of each quantity within the applicable delivery period specified above."

Should this statement be in Section M.B.(3).a. regarding Task Order 2 - ORS-8 Space Segment Schedule? Is this part of the evaluation criteria?

A: The requirement of FAR 52.211-8 Alt I, Time of Delivery for Task Order 2, applicable to the delivery of the SV, will be assessed for responsiveness as stated in the clause and will not be evaluated separately as part of Section M.

The approach to scheduling the overall activities of the project will be evaluated as part of Section M.

27. Q: In the ORS-8 Model Task Order under "T.1 Supplies and Services to be Provided" the contract type for CLIN 0001 is CPFF (pg 2), but clause "1852.216- 88 Performance Incentive (April 2015)" implies CLIN 0001 Space Vehicle will have an Incentive Fee.

Is CLIN 0001 CPFF or CPFF/IF (to include both fixed fee and incentive fee)?

A: CLIN 0001 on Task Order 2 is CPFF. In accordance with NFS 1816.402-270, technical performance incentives are required for hardware over $25M and indicates, “For a CPFF contract, the sum of the maximum positive performance incentive and fixed fee shall not exceed the limitations in FAR 15.404-4(c)(4)(i).”

28. Q: What is the cap or target contract value for Task Order 1?

A: As stated in the Cost/Price Template Exhibit 2a, the total FFP of Task Order 1 is not to exceed $200,000.

ORS-8 Space Segment Statement of Work (SOW)

29. Q: The ORS-8 Space Segment Statement of Work Appendix D states that “The SSPEDI SpS offerors shall use the Level 2 WBS as the basis for their proposed WBS” but also requires that “The offeror’s full WBS should be consistent with Space Systems WBS as defined in MIL-STD-881C.”

The Level 2 WBS table provided in Appendix D is inconsistent with MIL-STD- 881C. The WBS Summary in Attachment 4 and Attachment 5 are inconsistent with MIL-STD-881C required in Appendix D.

A: The ORS-8 Space Segment Appendix D provides the WBS Levels 1 & 2. The offerors should use MIL-STD-881C as a guide for developing Levels 3 & 4. The language in Appendix D has been modified to clarify, and the Resource Workbook (J.1(b)Attachment 5) has been modified to remove specific WBS Level 3 titles. The offerors are directed to use their own proposed Level 3 WBS in the Resource Workbook.

30. Q: ORS-8 Space Segment SOW APPENDIX D: CONTRACT WORK BREAKDOWN

STRUCTURE (CWBS)

The table below defines the Level 2 Contract Work Breakdown Structure (CWBS)associated with the ORS-8 Space Segment Task Order. The SSPEDI SpS offerors shall use this Level 2 WBS as the basis for their proposed WBS in response to the RFP. The offeror’s full WBS should be consistent with Space Systems WBS as defined in MIL-STD-881C “Work Breakdown Structures for Defense Materiel Items.” Appendix D of the ORS-8 SOW (defines the WBS down to level 2) and Attachment 5 of the Resource Workbook (defines the WBS down to level 3) clearly specifies the WBS structure down to level 3.

A: See the answer to Question #29.

31. Q: The ORS-8 Space Segment SOW Section 3.4.2.2 states that the Flight Vehicle Testbed (FVT) shall include an Engineering Development Unit (EDU) processor as well as engineering units for all other functions (e.g., star trackers, IMUs, solar array, transceivers, DRO, and sensors) and flight software.

Is the intent to allow contractors to follow their existing design practices and allow contractor discretion to procure engineering units of "other functions" (e.g., Star tracker, IMU, solar array, transceivers, DRO and sensors) as necessary to support these practices?

A: The design of the FVT is up to the contractor’s discretion, so long as it is “capable of replicating full functionality of the SV,” as stated in the ORS-8 Space Segment SOW Section 3.4.2.2.

32. Q: Can a complete listing on available NASA/NOAA Ground Stations be provided?

A: It is the contractor’s responsibility to identify elements of the existing data downlink and delivery architecture and determine whether that architecture is viable for their proposed design (ORS-8 Space Segment SOW Section 2.4.2)

33. Q: Can the government clarify what equipment is included in the "cryptographic equipment" noted on the GFE list, (i.e. is this space vehicle equipment, ground processing equipment. etc.?)

A: The Government will provide all the required Cryptographic Equipment as GFE for the ORS-8 Space Segment task order. However, the actual components of the equipment provided will largely depend on the offeror’s proposed solution architecture. Therefore, it is not possible for the Government to describe the details of that equipment prior to award.

34. Q: Para 2.3.2.2 of the ORS-8 Space Segment SOW states "MDM includes the capability to downlink, deliver, and complete initial processing of the WxD at the Weather Data Processing Center. MDM may include use of the existing Government baseline data downlink and delivery architecture".

Are terrestrial communications between "NOAA/NASA GND Stations and "Data Processing Facility" (i.e. green line on OV-1) provided GFE?

A: Existing Government capabilities can be leveraged (ORS-8 Space Segment SOW Section 3.4.4.2). The term “baseline” has been removed from the description of the existing Government architecture in the ORS-8 Space Segment SOW, since it was not the Government’s intent to suggest that all or part of the existing Government architecture should or must be part of the offeror’s solution.

35. Q: Para 2.4 of the ORS-8 Space Segment SOW states "The GS consists of...the National Air and Space Administration (NASA)/ National Oceanic and Atmospheric Administration (NOAA) Ground Station for WxD reception.”

Does the NASA/NOAA ground stations include all the NASA NEN stations identified at https://www.nasa.gov/directorates/heo/scan/services/networks/nen, or a subset of those, or just what is used currently by DMSP?

A: It is up to the offeror to determine and validate the WxD downlink infrastructure.

36. Q: Can the USG confirm that $175M is budgeted for entire ORS-8 mission (Space Segment, Ground Segment (not procured via SpS), Launch Segment (not procured via SpS), and first year of operations)? Does it include the funding of the customers program office? If not, Can USG identify SpS Task Order 2 budget?

A: The $175M is the total program cost identified in the CRD. The Government will not provide an estimate for the cost of the ORS-8 Space Segment Task Order.

37. Q: The ORS-8 Space Segment SOW Appendix D CWBS states offers shall use the Level 2 WBS given and that the offer’s full WBS should be consistent with MIL- STD-881C. Should Appendix D be renumbered with Launch Services Integration as 1.2.7 and Mission Ops as 1.2.9 per the MIL-STD?

A: See the answer to Question #29.

38. Q: The text references spacelink between the DRO MARK IVB, FMQ-17, and SMQ- 11 DRO terminals. The Technical Document Library does not provide ICD for these interfaces. Can the latest version of the SV to DRO terminal ICD(s) be made available to offerors?

A: Information about the MARK IVB is provided in the Technical Document Library (ICD_MDS_CDFSII_r2.2_Final.pdf). ICDs for the other systems are not currently available and will be provided after award.

39. Q: The WBS provided in the bidding instructions for CLIN 0002 Mission Operations is 1.6. Is it the Customer’s intent for the same WBS (1.6) to be used in CLIN 0003 Option 1, and CLIN 0004 Option 2? Please obtain confirmation.

A: Yes, CLINs 003 and 004 are associated with the work under WBS 1.6 (ORS-8 Space Segment SOW Section 3.6). See the instructions for the Cost/Price volume in Section L of the RFP.

40. Q: The provided/required TO2 WBS, corresponding SOW, and Resource Workbook do not align with the MIL-STD-881C Space Systems WBS required.

A: See the answer to Question #29.

41. Q: Flight Vehicle Testbed (FVT), you request “Engineering Development Unit (EDU) processor as well as engineering units for all other functions (e.g., star trackers, IMUs, solar array, transceivers, DRO, and sensors) and flight software.”” Does this include:

1) Radios (e.g. S-Band Radio)

2) Encryption

A: Yes, however, Cryptographic Controlled Items will be provided as GFE (ORS-8 Space Segment SOW, Section 4.3). Also, see the answer to Question #31

42. Q: What are the expected delivery dates for the GFP, i.e. Cryptographic Equipment, Energetically Charged Particle (ECP) payload?

A: The GFP will be delivered by identified need dates in accordance with the contractor’s proposed IMS. The ORS-8 Government Furnished Property List will be updated

43. Q: The final RFP states that “Cryptographic Equipment” will be provided, but the draft RFP stated that “Encryption Devices and Associated Keys” will be provided.

What is included with the cryptographic equipment and does it include encryption devices and keys?

A: Yes, the Cryptographic Equipment includes encryption devices and keys. The language in the ORS-8 Space Segment SOW has been updated.

44. Q: Data Downlink and Delivery of the Weather Ground system: Can the equipment associated with the Government architecture for the data downlink and delivery (McMurdo Gnd Stn, NSOF, and 557th WW) be assumed to be used cost free?

A: Yes, the use of existing ground architecture infrastructure can be leveraged.

Also see ORS-8 Space Segment SOW 3.4.4.2.

45. Q: Regarding the Flight Vehicle Testbed, ORS-8 Space Segment SOW Section

2.3.3.2 sub-bullet 4 reads “Verify commanding and telemetry at full data rates and bandwidth linked by hardline with the TT&C ground system”.

Can hardlined be clarified with regards to interface protocol?

A: "Hardline" implies a physical "wired" connection between the FVT and MMSOC to test TT&C capabilities. The actual connection type is for the offeror to determine.

46. Q: Regarding the Flight Vehicle Testbed, ORS-8 Space Segment SOW Section

2.3.3.2 sub-bullet 9 reads “Allow for breakout points to monitor signals, voltages, currents from multiple locations, and phases”.

What is meant by phases? Also, where are the breakout points sought: should we assume at the interface between the bus and the other components?

A: The reference to “phases” has been removed from the ORS-8 Space Segment SOW. The FVT must be capable of replicating full functionality of the SV (ORS- 8 Space Segment Section 3.4.2.2. It is up to the contractor to determine the necessary interface architecture to support that requirement.

47. Q: Regarding the Flight Vehicle Testbed, ORS-8 Space Segment SOW Section

2.3.3.2 sub-bullet 10 reads “Be able to integrate and functionally test flight hardware, including the weather payload, radio, GPS receiver, attitude determination system, and command and data handler”.

Can you clarify that it is intended to mate the Flight Payload with the Bus Sim in the FVT? Also, can you clarify if it is intended to mate the Flight Bus with the Payload Sim in the FVT?

A: Testing capability should be sufficient to replicate the full functionality of the SV.

It is up to the contractor to determine the necessary FVT architecture.

48. Q: If a contractor bids more than $175M (Space Vehicle/Launch Segment/Ground Segment/GSE/FVT) will the proposal be deemed non-compliant?

A: The $175M amount indicated in the CRD is in reference to the total program budget, including the ground and launch segments not procured through the SSPEDI SpS contract and is only provided as a guidance document. The Government will evaluate the offeror’s Cost/Price proposal in accordance with Section M. Also see the answer to Question #36.

49. Q: Will a copy of the ECP sensor and associated GSE delivery schedule be provided? If so, when?

A: GFP will be delivered by identified need dates in accordance with the contractor’s proposed IMS. Also see the answer to Question #42.

52. Q: Can the Government provide a copy of the Program Protection Plan (PPP) even if in draft form, or at least identify what is considered CPI for this program?

A: No. The contractor’s design informs the PPP and applicable CPI.

53. Q: Since Neptune is a component of the Govt Reference Architecture for MMSOC 2.1, does the Government intend to provide as GFE Neptune for use by the space segment for Telemetry, Tracking and Commanding, and therefore MUS development?

A: It is anticipated that the Government will not provide Neptune as GFE.

54. Q: The ORS-8 OV-1 indicates that stored mission data is transmitted from the ORS- 8 SV to the NOAA/NASA ground stations and TT&C to the AFSCN. SOW paragraph 2.4 describes the use of the AFSCN for TT&C. Paragraph 2.4.2 does not mention AFSCN use for stored mission data in the baseline Government architecture. Is the AFSCN not to be used for stored mission data downlink and delivery?

A: As stated in ORS-8 Space Segment SOW Section 3.4.4.2, it is the contractor’s responsibility to determine if the existing Government data downlink and delivery architecture is insufficient to support the contractor’s solution.

55. Q: Is communications from ground stations to data processing facilities included in the baseline Government architecture?

A: Yes, the existing Government data downlink and delivery architecture includes communication links, however, it is up to the offeror to determine if the existing system is sufficient for their proposed architecture. The term “baseline” has been removed from the description of the existing Government architecture in the ORS-8 Space Segment SOW, since it was not the Government’s intent to suggest that all or part of the existing Government architecture should or must be part of the offeror’s solution. Also see the answer to Question #44 and the ORS-8 Space Segment SOW Section 3.4.4.2.

56. Q: Are sites used with NOAA JPSS - sites at Svalbard and Troll in Antarctica -included in the baseline Government architecture?

A: No. However, the Contractor may consider leveraging existing architectures or propose new architecture elements. It is expected that the contractor will provide sufficient detail to validate their architectural solution.

57. Q: The description of the deliverable item (ORS-8 Space Segment SOW, Table 1) indicates that only software is to be delivered - “software to format mission data for delivery to the WxD processing center dissemination server”. However, Paragraph 4.3 GFE does not list any GFE hardware for the WxD processing center dissemination server or characteristics of such hardware. Is it the Government’s intention to supply WxD processing hardware or is the contactor to supply hardware as well as software for WxD Processing?

A: As stated in ORS-8 Space Segment SOW Section 3.4.4.2, it is the contractor’s responsibility to determine if the existing Government data downlink and delivery architecture is insufficient to support the contractor’s solution. Also see answer to Question #34

58. Q: What data is to be sent from MMSOC to JSpOC/National Space Center via ELSAT and SSA data flow?

A: Guidance is contained in the MMSOC 2.1 Service Interface Specification Document (sections 1.4.1.2 and 11.1.3), provided in the Technical Document Library.

ORS-8 Space Segment Technical Requirements Document (TRD)

59. Q: SSTRD-15 states: “The ORS-8 System shall produce infrared data products with a radiometric MWIR and LWIR channel accuracy of 0.12 K° at 300 K. This parameter is in the trade space for improved performance. Performance of channel accuracy greater than 0.12 K° over the sensitivity range will be considered non-compliant.”

a. Can you confirm that SSTRD-15 is specifying a radiometric precision, i.e.

NEdT?

b. Can you confirm the specification needs to be met when viewing a 300K scene, not across the entire sensitivity range?

A: a. SSTRD-15 is specifying radiometric accuracy. NEdT is one such measure.

b. Yes, the specification needs to be met when viewing a 300K scene.

60. Q: SSTRD-10 specifies the required horizontal cell size (HCS).

a. Please confirm that HCS is defined as found in the IORD-II:

For a parameter which is an estimate of the uniform spatial average of an environmental parameter over a square region of the earth’s surface or within a square layer of the atmosphere, the side length of this square region or layer.

(For a parameter which is an estimate of an environmental parameter at a point, the horizontal cell size is defined to be zero.) For a reported parameter not of this type but which is defined for a square region of the Earth’s surface or a square layer of the atmosphere (e.g., cloud cover, ice concentration, etc.), the side length of this square region.

A: This is an acceptable definition, but the Government is not going to prescribe a specific definition.

61. Q: SSTRD-10 states that the ORS-8 System cloud sensor sampling horizontal cell size (HCS) shall be equal to or less than 2 km at any point in the scan for all bands. This parameter is in the trade space for improved performance.

Performance of greater than 2.7 km will be considered non-compliant.

Is an FOV projection at the edge of scan forming a parallelogram with one altitude ≤ 2.7 km (i.e., the length of the side of the largest square area contained within the IFOV projection) and the other altitude > 2.7 km compliant?

Suggest providing a calculation definition (or calculation example) to make a consistent interpretation.

A: No. The HCS requirement applies to both horizontal axes, not just one.

62. Q: The ORS-8 SSTRD15 states that the ORS-8 System shall produce infrared data products with a radiometric MWIR and LWIR channel accuracy of 0.12 K° at 300 K. This parameter is in the trade space for improved performance. Performance of channel accuracy greater than 0.12 K° over the sensitivity range will be considered non-compliant.

Is the intent to specify a noise equivalent differential temperature (NEDT), rather than a measurement accuracy?

A: SSTRD15 is specifying radiometric accuracy. NEdT is one such measure.

63. Q: SSTRD-34: Does "The SV shall have an on-orbit mission design life of full capability for three years at least 80% confidence" mean the SV shall have a probability of success (Ps) of greater than or equal to 0.80 at the end of the 3 year design life?

A: Yes, that is an accurate interpretation of the requirement.

64. Q: Section 2.2 of the ORS-8 TRD calls out the ORS-8 DRO ICD as a reference, but that document is not in the bidder’s library. Can you supply the ORS-8 DRO

ICD?

A: The ORS-8 DRO ICD is a CDRL item (#12) that the contractor is responsible for producing. See ORS-8 Space Segment SOW, Section 3.3.7.

65. Q: SSTRD-75 and SSTRD-81 state that the MDM should "disseminate the products to the weather centrals".

Is it correct to assume the weather centrals are NOAA/NSOF in Suitland, MD and 557W in Omaha?

Are there any other sites?

A: The “weather centrals” are defined and listed in the ORS-8 Space Segment TRD glossary.

66. Q: SSTRD-15 states: "The ORS-8 System shall produce infrared data products with a radiometric MWIR and LWIR channel accuracy of 0.12 K° at 300 K. This parameter is in the trade space for improved performance. Performance of channel accuracy greater than 0.12 K° over the sensitivity range will be considered non-compliant." SSTRD-16 states: "The ORS-8 System shall produce MWIR and LWIR infrared data products with a sensitivity range of 180 – 320 K." One of the bands required by SSTRD-08 is a 3.7 micron band that has very low signal for brightness temperatures less than 240 K.

Is the intent of SSTRD-15 to require that a radiometric accuracy of 0.12K be provided at 300K, or is it to require that a radiometric accuracy of 0.12K be provided at any scene temperature between 180K and 320K for all spectral bands?

A: Yes, the intent of SSTRD-15 is to require that a radiometric accuracy of 0.12K be provided at 300K.

67. Q: Please provide the Mark IVB (UMQ-13), AN/SMQ-11, and FMQ-17 Interface Control Documents (ICDs) or the ORS-8 DRO ICD?”

A: Please reference the documents provided in the Technical Document Library (TDL). The TDL has been updated with additional documentation. The ORS-8 Space Segment DRO ICD is a CDRL item (#12), which the contractor is responsible for producing.

68. Q: The SSTRD-15 specifies radiometric MWIR and LWIR channel accuracy of 0.12 K° at 300 K. The requirement continues to describe this parameter as “in the trade space for improved performance” and specifies the required accuracy across a sensitivity range of 180-320 K. Achieving this level of radiometric accuracy in the LWIR across this range is possible, and encompasses a range of detector options from cooled to uncooled. Extending this requirement into the MWIR (3 - 8 mm) will significantly limit the detector trade space and drive cost and schedule.

A: The requirement is accurate as stated. Also see the answer to Question #59.

69. Q: The SSTRD-14 specifies a series of uncertainty requirements for the Cloud Top Temperature (CTT) data products. However, the ORS-8 SOW does not require development/delivery of final data products (EDRs), only for RDRs and SDRs. If the offeror is providing a sensor system with heritage LWIR bands that meet the radiometric requirements specified in SSTRD-15 for those relevant LWIR bands, is this sufficient to demonstrate compliance to the SSTRD-14 requirement?

A: No. SSTRD-15 addresses payload data performance whereas SSTRD 14 is a space segment level performance requirement.

70. Q: The TRD refers to multiple requirements parameters as a baseline and "trade space". If an offeror is within the "trade space", is that a strength or significant strength?

A: RFP Section M.3(a)B(3) describes how the Government will evaluate offerors’ proposal with respect to the Critical Performance Parameters.