NSST_QA_Tracker_Set_3_Ver_1(1MAR2017).xlsx
XLSX spreadsheet 60 KB Posted
- Attached to
- SURFACE NAVIGATION, SEAMANSHIP, AND SHIPHANDLING TRAINING (NSST) SYSTEMS AND SUPPORT Federal contract opportunity
- Solicitation number
- N6134017R0020
About this file
NSST QA Tracker Set 3 Ver 1(1MAR2017)
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| NSST_Post_Industry_Day_Notice.docx | DOCX document | |
| NSST_Draft_Phase_I_Posting.docx | DOCX document |
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
Notes
| Notes |
| Responses are subject to change. Any responses to subsequent question sets shall supersede responses herein. |
| Nothing in these responses supersedes requirements as stated in the solicitation. |
| Some questions have been paraphrased from verbal industry day questions. |
A-RFP
| Item # | Subject | Question/Comment/Request/Recommendation | Reference(s) | Date | Government Response | Response Date | A | |
| A-1 | Eliminating projector based systems | Particularly in view of the Government's decision to provide no GFP/M/E/I, request the Government consider eliminating SOW/PRF requirements for visual projection systems and for separate bridge Wing training devices/systems (physical trainer configurations). | ||||||
| Will the Government consider revising the PRF to eliminate the need for projector based systems? This would potentially allow for alternative visual solutions such as AR/VR, which would result in much greater deployability and life cycle cost savings. | L 2.2.1.2.3 and others in SPEC | 27-Feb-17 | The Government's position is that the current display system requirements provide the desired level of trade space for innovation while supporting existing training courses and stakeholder expectations. | 1 | ||||
| A-2 | Database Design | Can the Navy provide more detail for the database design or upgrade to aid pricing. As written there is latitude. | 27-Feb-17 | The Government is investigating adding more specific database development bounds to possibly include the number and types of databases based on level of complexity. | 2 | |||
| A-3 | Innovation | 1) We acknowledge that draft RFP Section L, PART A, 1.0 General, specifies "Alternate proposals are not acceptable." However, as allowed by FAR 15.209(a)(2), request the Government consider adding 52.215-1 Alt II para (c)(9) to the solicitation. This would allow for the acceptance of alternate proposals that satisfy the defined NSS training needs, provide clear advantage to the Government, provide fresh, innovative approaches to integrated software and hardware capabilities unconstrained by legacy carryover performance specifications, and deliver a favorable total ownership cost advantage. | ||||||
| 2) What is the Government's intent for leveraging new technologies and innovations in training into the NSS training product line? Is there a product line improvement or innovation roadmap? The DRFP Section L and Section M reflect the importance of innovation in the IDIQ capabilities and the DO1 technical proposal, but the aperture for innovation in this solicitation is constrained by the legacy carryover in the performance specifications. | Section L, PART A, 1.0 General; end of first paragraph | 27-Feb-17 | 1) The Government does not currently intend to allow alternate proposals. |
2) The Government views the move towards a modular architecture as an enabler to future technology incorporation when that technology proves practical and beneficial to meeting training requirements.
| 3 | ||
| A-4 | Scoring innovation and use of alternative solutions | Training system design approach refers to evaluating solutions for both innovation and conformity to spec. The Government seems to be specifying a solution in some instances (e.g. use of projector based solutions). This precludes innovative solutions in some instances (e.g. use of projector based solutions). This precludes innovative solutions such as networked VR. |
1) How will the Government score and value innovation?
| 2) Would the Government consider alternatives to existing legacy approaches to training? | 1.2.1.2 Element 2 | 27-Feb-17 | 1) The proposal rating mechanisms available to the Government are those defined in Section M "Evaluation Factors for Award" of the solicitation. | ||||
| 2) The Government's position is that the current system requirements provide the desired level of trade space for innovation while supporting existing training courses and stakeholder expectations. | 4 | ||||||
| A-5 | Demo Video | Recommendation: Either mandate a demo video to be provided or remove requirement completely. Rationale: this will ease Government evaluation and not favor one bidder over another | 27-Feb-17 | The Government anticipates requiring a video. | 5 | ||
| A-6 | Contract CLINs | Can the Government please explain the relationship of the Basic Award CLINS 1001-2005 and to DO1 CLINS 0001-0004? | |||||
| Another way of asking - DO1 CLINS - what basic award CLIN is these covered by? | 27-Feb-17 | The delivery order has a parent child relationship where every delivery order has a parent basic award CLIN and children CLINs with specific tasking. DO1 CLINs 0001-0004 are currently children to Delivery Order 1 and Delivery Order 1 will likely be a child to Basic Award CLIN 1002. | 6 | ||||
| A-7 | Factor/subfactors | Is Factor level a roll-up of subfactors? | Slide 15 | 27-Feb-17 | Yes. | 7 | |
| A-8 | Visualization system design | Will Visualization system design cover NSST-1 through 5? | Slide 18 | 27-Feb-17 | One software baseline will support all NSST-1 through NSST-5 configurations. The visualization system design needs to cover all NSST-1 through NSST-5 configurations. | 8 | |
| A-9 | Government Ownership Evaluation | How will Government ownership be evaluated? |
How will the difference in using COTS stuff and proprietary stuff be weighed?
Typically there is not Government not ownership, but only licensing; Can you explain Government’s concept?
Request clarification on the meaning of Government Ownership vs Government use via licensing since ownership term is not commonly used.
Do not understand how ownership will be evaluated fairly. Slide 21 27-Feb-17 A) Solicitation Section M, Subfactor 3 identifies how the Government will evaluate Government Ownership.
B) Solicitation Section M, Part A, 3.0 identifies the weighting of evaluation factors and subfactors.
C) The Government is analyzing the use of the term "Ownership" in the solicitation and associated attachments (i.e.. SOW/PRF). Revisions to documents where usage of the term "Ownership" exist will occur as appropriate.
| D) All offerors proposals will be evaluated in accordance with the criterion identified in Solicitation Section M, Subfactor 3. | 9 | ||||||
| A-10 | Limited vs detailed designs | Can you expand on limited vs detail design | Slide 25 | 27-Feb-17 | On industry day presentation slide #25, "Limited scope of design" means the requirements for site specific designs was reduced from a list of 12 sites to 2 sites (San Diego, CA and Newport, RI). | ||
| On industry day presentation slide #25, detailed design is equivalent to product baseline which includes site specific installation designs for all San Diego, CA and Newport, RI devices. | 10 | ||||||
| A-11 | Visual equipment GFP | 1) Is the assumption/direction of pricing of item without the benefit of GFP/GFE explicit in the pricing directions? | |||||
| 2) Will visual equipment be provided as GFP? | 27-Feb-17 | No GFP/GFE will be provided for this contract. | 11 | ||||
| A-12 | Instant award | Is the instant award CLINs 1-4? | 27-Feb-17 | At time of award, the ID/IQ contract "Basic Award" will be made. At the same time, Delivery Order 0001 (DO 0001) will be awarded. DO 0001 is also known as the "Instant Award". CLIN 0001 is the only guaranteed CLIN to be funded at time of award. | 12 | ||
| A-13 | Attachment L-1 spreadsheet | How will evaluations be done for Attachment L-1 price information? | Attachment L-1 spreadsheet | 27-Feb-17 | Solicitation Section M, Part B, Price, identifies how the Government will evaluate the Price Proposal. | 13 | |
| A-14 | Equivalent | How will things be evaluated if all technical proposals are at the same level? Will there be only equal but difference in price? Are there discriminators? | 27-Feb-17 | Solicitation Section M, Part A, 3.0 identifies the weighting of evaluation factors and subfactors. | 14 | ||
| A-15 | Milestone payments | Standard payment in contract; will milestone payments be acceptable? | 27-Feb-17 | Progress Payments are identified as the method of contract financing available for the contract. Performance Based Payments are not currently authorized. | 15 | ||
| A-16 | Price evaluation | 1) How will the price factor be weighted? |
2) For price evaluations, how is analysis done?
3) How will total price is evaluated?
4) What about end of life items like projectors at end of 5 years?
5) What about determining price for main display refresh channels? 27-Feb-17 1) Solicitation Section M, Part A, 3.0 identifies the weighting of evaluation factors and subfactors.
2) Solicitation Section M, Part B, Price, identifies how the Government will evaluate the Price Proposal., additionally, see FAR Clause 52.215-1 INSTRUCTIONS TO OFFERORS -- COMPETITIVE ACQUISITION (JAN 2004) .
3) Solicitation Section M, Part B, Price, identifies how the Government will evaluate the Price Proposal.
4) Government position is that adequate data is available to establish projector refresh pricing.
5) Government position is that channels are the best way to price main display refreshes considering the variable number of channels used across existing devices utilizing projection technology.
| Note: The Government will consider language refinement to clarify the delineation between what work does and does not need to be accounted for. | 16 | ||
| A-17 | Small business | 1) How will Small business be evaluated? | |
| 2) Is SBU just DO1? | 27-Feb-17 | 1) Solicitation Section M, Part B, 1.1.8 identifies how the Government will evaluate Small Business Utilization. |
2) Small business utilization is just for the DO.
| Note: Small Business Utilization will be analyzed to determine if revisions to Sections L&M are appropriate. | 17 | |||
| A-18 | 18 | |||
| A-19 | 19 | |||
| A-20 | 20 | |||
| A-21 | 21 | |||
| A-22 | ||||
| 22 | ||||
| A-23 | 23 | |||
| A-24 | 24 | |||
| A-25 | 25 | |||
| A-26 | 26 | |||
| A-27 | 27 | |||
| A-28 | 28 | |||
| A-29 | 29 | |||
| A-30 | 30 | |||
| A-31 | 31 | |||
| A-32 | 32 | |||
| A-33 | 33 | |||
| A-34 | 34 | |||
| A-35 | 35 | |||
| A-36 | 36 | |||
| A-37 | 37 | |||
| A-38 | 38 | |||
| A-39 | 39 | |||
| A-40 | 40 | |||
| A-41 | 41 | |||
| A-42 | 42 | |||
| A-43 | 43 | |||
| A-44 | 44 | |||
| A-45 | 45 | |||
| A-46 | 46 | |||
| A-47 | 47 | |||
| A-48 | 48 | |||
| A-49 | 49 | |||
| A-50 | 50 | |||
| A-51 | 51 | |||
| A-52 | 52 | |||
| A-53 | 53 | |||
| A-54 | 54 | |||
| A-55 | 55 | |||
| A-56 | 56 | |||
| A-57 | 57 | |||
| A-58 | 58 | |||
| A-59 | 59 | |||
| A-60 | 60 | |||
| A-61 | 61 | |||
| A-62 | 62 | |||
| A-63 | 63 | |||
| A-64 | 64 | |||
| A-65 | 65 | |||
| A-66 | 66 | |||
| A-67 | 67 | |||
| A-68 | 68 | |||
| A-69 | 69 | |||
| A-70 | 70 | |||
| A-71 | 71 | |||
| A-72 | 72 | |||
| A-73 | 73 | |||
| A-74 | 74 | |||
| A-75 | 75 | |||
| A-76 | 76 | |||
| A-77 | 77 | |||
| A-78 | 78 | |||
| A-79 | 79 | |||
| A-80 | 80 | |||
| A-81 | 81 | |||
| A-82 | 82 | |||
| A-83 | 83 | |||
| A-84 | 84 | |||
| A-85 | 85 | |||
| A-86 | 86 | |||
| A-87 | 87 | |||
| A-88 | 88 | |||
| A-89 | 89 | |||
| A-90 | 90 | |||
| A-91 | 91 | |||
| A-92 | 92 | |||
| A-93 | 93 | |||
| A-94 | 94 | |||
| A-95 | 95 | |||
| A-96 | 96 | |||
| A-97 | 97 | |||
| A-98 | 98 | |||
| A-99 | 99 | |||
| A-100 | 100 |
B-SOW
| Item # | Subject | Question/Comment/Request/Recommendation | Reference(s) | Date | Government Response | Response Date | B |
| B-1 | SOW specification: Legacy systems | Is the removal of legacy systems as part of installation of new systems specified in the SOW? | 27-Feb-17 | The current DO1 SOW para 3.2.4 (OPTION Device Installation - San Diego, CA) contains the following requirement, "The contractor shall dispose of legacy equipment and furnishings removed during NSST device installation." | 1 | ||
| B-2 | GPI | Can the 15 miles requirement for GPI In-plant testing be relaxed to 20 miles? | 27-Feb-17 | The Government anticipates an increase to the GPI/JFI requirement to 20 miles. | 2 | ||
| B-3 | TSAR | Does the TSAR influence design? | 27-Feb-17 | Yes. Contractors are required to derive system requirements based on the performance requirements, baseline configuration audits, and the training system requirements workshop IAW the systems engineering process required in DO1 SOW. The TSAR cannot supersede the PRF. The Government retains the right to modify the contract through the RFV and ECP process when it is in the best interest of the Government. | 3 | ||
| B-4 | 4 | ||||||
| B-5 | 5 | ||||||
| B-6 | 6 | ||||||
| B-7 | 7 | ||||||
| B-8 | 8 | ||||||
| B-9 | 9 | ||||||
| B-10 | 10 | ||||||
| B-11 | 11 | ||||||
| B-12 | 12 | ||||||
| B-13 | 13 | ||||||
| B-14 | 14 | ||||||
| B-15 | 15 | ||||||
| B-16 | 16 | ||||||
| B-17 | 17 | ||||||
| B-18 | 18 | ||||||
| B-19 | 19 | ||||||
| B-20 | 20 | ||||||
| B-21 | 21 | ||||||
| B-22 | 22 | ||||||
| B-23 | 23 | ||||||
| B-24 | 24 | ||||||
| B-25 | 25 | ||||||
| B-26 | 26 | ||||||
| B-27 | 27 | ||||||
| B-28 | 28 | ||||||
| B-29 | 29 | ||||||
| B-30 | 30 | ||||||
| B-31 | 31 | ||||||
| B-32 | 32 | ||||||
| B-33 | 33 | ||||||
| B-34 | 34 | ||||||
| B-35 | 35 | ||||||
| B-36 | 36 | ||||||
| B-37 | 37 | ||||||
| B-38 | 38 | ||||||
| B-39 | 39 | ||||||
| B-40 | 40 | ||||||
| B-41 | 41 | ||||||
| B-42 | 42 | ||||||
| B-43 | 43 | ||||||
| B-44 | 44 | ||||||
| B-45 | 45 | ||||||
| B-46 | 46 | ||||||
| B-47 | 47 | ||||||
| B-48 | 48 | ||||||
| B-49 | 49 | ||||||
| B-50 | 50 | ||||||
| B-51 | 51 | ||||||
| B-52 | 52 | ||||||
| B-53 | 53 | ||||||
| B-54 | 54 | ||||||
| B-55 | 55 | ||||||
| B-56 | 56 | ||||||
| B-57 | 57 | ||||||
| B-58 | 58 | ||||||
| B-59 | 59 | ||||||
| B-60 | 60 | ||||||
| B-61 | 61 | ||||||
| B-62 | 62 | ||||||
| B-63 | 63 | ||||||
| B-64 | 64 | ||||||
| B-65 | 65 | ||||||
| B-66 | 66 | ||||||
| B-67 | 67 | ||||||
| B-68 | 68 | ||||||
| B-69 | 69 | ||||||
| B-70 | 70 | ||||||
| B-71 | 71 | ||||||
| B-72 | 72 | ||||||
| B-73 | 73 | ||||||
| B-74 | 74 | ||||||
| B-75 | 75 | ||||||
| B-76 | 76 | ||||||
| B-77 | 77 | ||||||
| B-78 | 78 | ||||||
| B-79 | 79 | ||||||
| B-80 | 80 | ||||||
| B-81 | 81 | ||||||
| B-82 | 82 | ||||||
| B-83 | 83 | ||||||
| B-84 | 84 | ||||||
| B-85 | 85 | ||||||
| B-86 | 86 | ||||||
| B-87 | 87 | ||||||
| B-88 | 88 | ||||||
| B-89 | 89 | ||||||
| B-90 | 90 | ||||||
| B-91 | 91 | ||||||
| B-92 | 92 | ||||||
| B-93 | 93 | ||||||
| B-94 | 94 | ||||||
| B-95 | 95 | ||||||
| B-96 | 96 | ||||||
| B-97 | 97 | ||||||
| B-98 | 98 | ||||||
| B-99 | 99 | ||||||
| B-100 | 100 |
C-PRF
| Item # | Subject | Question/Comment/Request/Recommendation | Reference(s) | Date | Government Response | Response Date | C |
| C-1 | Celestial requirements | Did you remove celestial requirements? | 27-Feb-17 | Requirements related to celestial navigation have been removed in the most recent draft PRF. | 1 | ||
| C-2 | Virtual Watchstander | What is virtual watchstander? | 27-Feb-17 | This is often referred to in legacy systems as speech recognition. See PRF 3.1.3.7. | 2 | ||
| C-3 | Visual System Requirements | Can any more information be provided on the new visual system requirements? | 27-Feb-17 | They are not intended to be highly restrictive, but are intended to preserve key performance parameters from legacy requirements. | 3 | ||
| C-4 | Industry Standard API | Can you add “industry standards” to API such as CIGI? Can we add “industry standards” to interface? | Slide 32 | 27-Feb-17 | The Government does not see how current requirements restrict the use of "industry standard" APIs. The current requirement is for the API to be "open, non-proprietary, and documented". | 4 | |
| C-5 | Development Seat | How does the development seat exist and how will it be used? | 27-Feb-17 | The development seat will be delivered with the initial article. The Government intends for the development seat to provide more long term use after the ID/IQ is complete, but the Government is not prohibited from using the development seat during the ID/IQ. The Government may use the development seat internally to conduct minor tweaks, but the more likely use case for the development seat is to support future efforts. | 5 | ||
| C-6 | Development Seat database support | Does the development seat need to support databases? | 27-Feb-17 | The development seat must meet the database development seat requirements in PRF 3.1.9.1 and must meet the verification requirement in PRF 4.3.9.b to procedurally construct runtime databases from source files provided IAW CDRL A003 (SPS). | 6 | ||
| C-7 | 7 | ||||||
| C-8 | 8 | ||||||
| C-9 | 9 | ||||||
| C-10 | 10 | ||||||
| C-11 | 11 | ||||||
| C-12 | 12 | ||||||
| C-13 | 13 | ||||||
| C-14 | 14 | ||||||
| C-15 | 15 | ||||||
| C-16 | 16 | ||||||
| C-17 | 17 | ||||||
| C-18 | 18 | ||||||
| C-19 | 19 | ||||||
| C-20 | 20 | ||||||
| C-21 | 21 | ||||||
| C-22 | 22 | ||||||
| C-23 | 23 | ||||||
| C-24 | 24 | ||||||
| C-25 | 25 | ||||||
| C-26 | 26 | ||||||
| C-27 | 27 | ||||||
| C-28 | 28 | ||||||
| C-29 | 29 | ||||||
| C-30 | 30 | ||||||
| C-31 | 31 | ||||||
| C-32 | 32 | ||||||
| C-33 | 33 | ||||||
| C-34 | 34 | ||||||
| C-35 | 35 | ||||||
| C-36 | 36 | ||||||
| C-37 | 37 | ||||||
| C-38 | 38 | ||||||
| C-39 | 39 | ||||||
| C-40 | 40 | ||||||
| C-41 | 41 | ||||||
| C-42 | 42 | ||||||
| C-43 | 43 | ||||||
| C-44 | 44 | ||||||
| C-45 | 45 | ||||||
| C-46 | 46 | ||||||
| C-47 | 47 | ||||||
| C-48 | 48 | ||||||
| C-49 | 49 | ||||||
| C-50 | 50 | ||||||
| C-51 | 51 | ||||||
| C-52 | 52 | ||||||
| C-53 | 53 | ||||||
| C-54 | 54 | ||||||
| C-55 | 55 | ||||||
| C-56 | 56 | ||||||
| C-57 | 57 | ||||||
| C-58 | 58 | ||||||
| C-59 | 59 | ||||||
| C-60 | 60 | ||||||
| C-61 | 61 | ||||||
| C-62 | 62 | ||||||
| C-63 | 63 | ||||||
| C-64 | 64 | ||||||
| C-65 | 65 | ||||||
| C-66 | 66 | ||||||
| C-67 | 67 | ||||||
| C-68 | 68 | ||||||
| C-69 | 69 | ||||||
| C-70 | 70 | ||||||
| C-71 | 71 | ||||||
| C-72 | 72 | ||||||
| C-73 | 73 | ||||||
| C-74 | 74 | ||||||
| C-75 | 75 | ||||||
| C-76 | 76 | ||||||
| C-77 | 77 | ||||||
| C-78 | 78 | ||||||
| C-79 | 79 | ||||||
| C-80 | 80 | ||||||
| C-81 | 81 | ||||||
| C-82 | 82 | ||||||
| C-83 | 83 | ||||||
| C-84 | 84 | ||||||
| C-85 | 85 | ||||||
| C-86 | 86 | ||||||
| C-87 | 87 | ||||||
| C-88 | 88 | ||||||
| C-89 | 89 | ||||||
| C-90 | 90 | ||||||
| C-91 | 91 | ||||||
| C-92 | 92 | ||||||
| C-93 | 93 | ||||||
| C-94 | 94 | ||||||
| C-95 | 95 | ||||||
| C-96 | 96 | ||||||
| C-97 | 97 | ||||||
| C-98 | 98 | ||||||
| C-99 | 99 | ||||||
| C-100 | 100 |
D-CDRLS
| Item # | Subject | Question/Comment/Request/Recommendation | Reference(s) | Date | Government Response | Response Date | D |
| D-1 | 1 | ||||||
| D-2 | 2 | ||||||
| D-3 | 3 | ||||||
| D-4 | 4 | ||||||
| D-5 | 5 | ||||||
| D-6 | 6 | ||||||
| D-7 | 7 | ||||||
| D-8 | 8 | ||||||
| D-9 | 9 | ||||||
| D-10 | 10 | ||||||
| D-11 | 11 | ||||||
| D-12 | 12 | ||||||
| D-13 | 13 | ||||||
| D-14 | 14 | ||||||
| D-15 | 15 | ||||||
| D-16 | 16 | ||||||
| D-17 | 17 | ||||||
| D-18 | 18 | ||||||
| D-19 | 19 | ||||||
| D-20 | 20 | ||||||
| D-21 | 21 | ||||||
| D-22 | 22 | ||||||
| D-23 | 23 | ||||||
| D-24 | 24 | ||||||
| D-25 | 25 | ||||||
| D-26 | 26 | ||||||
| D-27 | 27 | ||||||
| D-28 | 28 | ||||||
| D-29 | 29 | ||||||
| D-30 | 30 | ||||||
| D-31 | 31 | ||||||
| D-32 | 32 | ||||||
| D-33 | 33 | ||||||
| D-34 | 34 | ||||||
| D-35 | 35 | ||||||
| D-36 | 36 | ||||||
| D-37 | 37 | ||||||
| D-38 | 38 | ||||||
| D-39 | 39 | ||||||
| D-40 | 40 | ||||||
| D-41 | 41 | ||||||
| D-42 | 42 | ||||||
| D-43 | 43 | ||||||
| D-44 | 44 | ||||||
| D-45 | 45 | ||||||
| D-46 | 46 | ||||||
| D-47 | 47 | ||||||
| D-48 | 48 | ||||||
| D-49 | 49 | ||||||
| D-50 | 50 | ||||||
| D-51 | 51 | ||||||
| D-52 | 52 | ||||||
| D-53 | 53 | ||||||
| D-54 | 54 | ||||||
| D-55 | 55 | ||||||
| D-56 | 56 | ||||||
| D-57 | 57 | ||||||
| D-58 | 58 | ||||||
| D-59 | 59 | ||||||
| D-60 | 60 | ||||||
| D-61 | 61 | ||||||
| D-62 | 62 | ||||||
| D-63 | 63 | ||||||
| D-64 | 64 | ||||||
| D-65 | 65 | ||||||
| D-66 | 66 | ||||||
| D-67 | 67 | ||||||
| D-68 | 68 | ||||||
| D-69 | 69 | ||||||
| D-70 | 70 | ||||||
| D-71 | 71 | ||||||
| D-72 | 72 | ||||||
| D-73 | 73 | ||||||
| D-74 | 74 | ||||||
| D-75 | 75 | ||||||
| D-76 | 76 | ||||||
| D-77 | 77 | ||||||
| D-78 | 78 | ||||||
| D-79 | 79 | ||||||
| D-80 | 80 | ||||||
| D-81 | 81 | ||||||
| D-82 | 82 | ||||||
| D-83 | 83 | ||||||
| D-84 | 84 | ||||||
| D-85 | 85 | ||||||
| D-86 | 86 | ||||||
| D-87 | 87 | ||||||
| D-88 | 88 | ||||||
| D-89 | 89 | ||||||
| D-90 | 90 | ||||||
| D-91 | 91 | ||||||
| D-92 | 92 | ||||||
| D-93 | 93 | ||||||
| D-94 | 94 | ||||||
| D-95 | 95 | ||||||
| D-96 | 96 | ||||||
| D-97 | 97 | ||||||
| D-98 | 98 | ||||||
| D-99 | 99 | ||||||
| D-100 | 100 |
E-OTHER
| Item # | Subject | Question/Comment/Request/Recommendation | Reference(s) | Date | Government Response | Response Date | E |
| E-1 | Development Seat | How/where is training for Government personnel covered for the development seat? | Slide 32 | 27-Feb-17 | No special training courses are required for the Development Seat. The Government may establish a Development Seat training course requirement in a future delivery order, but currently has no intention to do so. The Government's assumption is that the end user of the Development Seat will be an appropriately experienced and skilled person (e.g. database developer, programmer, etc.). Additionally, the Government engineering team will learn about the Development Seat functionality through the design and testing of the Development Seat. | 1 | |
| E-2 | One-on-One meetings | Can a 30 minute one-on-one meeting be scheduled in the near future, prior to final RFP release? | 27-Feb-17 | One-on-One meetings are not available. The Government believes that the use of questions, comments, requests, and recommendations provide an adequate vehicle for communication following the site visits and industry day event. | 2 | ||
| E-3 | Pre-solicitation questions/feedback | Is the 6th of March deadline for Pre-solicitation questions/feedback accurate? | 27-Feb-17 | Yes, please see the NSST Post Industry Day Notice. | 3 | ||
| E-4 | Updated technical package | Will there be updates to the technical package be provided? | 27-Feb-17 | Please see the NSST Post Industry Day Notice. | 4 | ||
| E-5 | Alternative requirements | Were alternative requirements entertained at any point? | 27-Feb-17 | The Government has established the desired technical performance requirements based on stakeholder requirements utilizing internal processes that considered numerous alternatives. | 5 | ||
| E-6 | 6 | ||||||
| E-7 | 7 | ||||||
| E-8 | 8 | ||||||
| E-9 | 9 | ||||||
| E-10 | 10 | ||||||
| E-11 | 11 | ||||||
| E-12 | 12 | ||||||
| E-13 | 13 | ||||||
| E-14 | 14 | ||||||
| E-15 | 15 | ||||||
| E-16 | 16 | ||||||
| E-17 | 17 | ||||||
| E-18 | 18 | ||||||
| E-19 | 19 | ||||||
| E-20 | 20 | ||||||
| E-21 | 21 | ||||||
| E-22 | 22 | ||||||
| E-23 | 23 | ||||||
| E-24 | 24 | ||||||
| E-25 | 25 | ||||||
| E-26 | 26 | ||||||
| E-27 | 27 | ||||||
| E-28 | 28 | ||||||
| E-29 | 29 | ||||||
| E-30 | 30 | ||||||
| E-31 | 31 | ||||||
| E-32 | 32 | ||||||
| E-33 | 33 | ||||||
| E-34 | 34 | ||||||
| E-35 | 35 | ||||||
| E-36 | 36 | ||||||
| E-37 | 37 | ||||||
| E-38 | 38 | ||||||
| E-39 | 39 | ||||||
| E-40 | 40 | ||||||
| E-41 | 41 | ||||||
| E-42 | 42 | ||||||
| E-43 | 43 | ||||||
| E-44 | 44 | ||||||
| E-45 | 45 | ||||||
| E-46 | 46 | ||||||
| E-47 | 47 | ||||||
| E-48 | 48 | ||||||
| E-49 | 49 | ||||||
| E-50 | 50 | ||||||
| E-51 | 51 | ||||||
| E-52 | 52 | ||||||
| E-53 | 53 | ||||||
| E-54 | 54 | ||||||
| E-55 | 55 | ||||||
| E-56 | 56 | ||||||
| E-57 | 57 | ||||||
| E-58 | 58 | ||||||
| E-59 | 59 | ||||||
| E-60 | 60 | ||||||
| E-61 | 61 | ||||||
| E-62 | 62 | ||||||
| E-63 | 63 | ||||||
| E-64 | 64 | ||||||
| E-65 | 65 | ||||||
| E-66 | 66 | ||||||
| E-67 | 67 | ||||||
| E-68 | 68 | ||||||
| E-69 | 69 | ||||||
| E-70 | 70 | ||||||
| E-71 | 71 | ||||||
| E-72 | 72 | ||||||
| E-73 | 73 | ||||||
| E-74 | 74 | ||||||
| E-75 | 75 | ||||||
| E-76 | 76 | ||||||
| E-77 | 77 | ||||||
| E-78 | 78 | ||||||
| E-79 | 79 | ||||||
| E-80 | 80 | ||||||
| E-81 | 81 | ||||||
| E-82 | 82 | ||||||
| E-83 | 83 | ||||||
| E-84 | 84 | ||||||
| E-85 | 85 | ||||||
| E-86 | 86 | ||||||
| E-87 | 87 | ||||||
| E-88 | 88 | ||||||
| E-89 | 89 | ||||||
| E-90 | 90 | ||||||
| E-91 | 91 | ||||||
| E-92 | 92 | ||||||
| E-93 | 93 | ||||||
| E-94 | 94 | ||||||
| E-95 | 95 | ||||||
| E-96 | 96 | ||||||
| E-97 | 97 | ||||||
| E-98 | 98 | ||||||
| E-99 | 99 | ||||||
| E-100 | 100 |
File details come from the government source that posted it. Updated .