Technical_Questions_Set_11.pdf

PDF 106 KB Posted

Attached to
A-10 Technical Order Engineering Support
Solicitation number
FA8202-16-R-1000
Issued by

About this file

Technical Questions Set 11

View the file

Other files

File Type Posted
FA820216R1000_______0006.pdf PDF
RFP_Attachment_16-Task_Order__1_PWS.pdf PDF
CDRL_A008_TMCR.pdf PDF
RFP_Attachment_2-Section_M_A10_TO_Support.pdf PDF
RFP_Attachment_1-Section_L_A10_TO_Support.pdf PDF
RFP_Attachment_20_TMCR_TM-86-01P_Change_Package.pdf PDF
RFP_Attachment_19_TOLCMP_Guide.pdf PDF
RFP_Attachment_12-PWS.pdf PDF
RFP_Attachment_12-Performance_Work_Statement.pdf PDF
RFP_Attachment_3-Sample_Task_1.pdf PDF
RFP_Attachment_17-Task_Order_1_CDRLs.pdf PDF
RFP_Attachment_11-Pricing_Worksheet_and_Task_Order_1_Proposed_Pricing.xls XLS spreadsheet
Solicitation_CDRLs.pdf PDF
RFP_Attachment_1-Section_L_A10_TO_Support.pdf PDF
RFP_Attachment_16-Task_Order__1_PWS.pdf PDF
RFP_Attachment_5-Sample_Task_3.pdf PDF
RFP_Attachment_18-TOLCMP_A-10.pdf PDF
FA820216R1000_______0005.pdf PDF
RFP_Attachment_4-Sample_Task_2.pdf PDF
RFP_Attachment_2-Section_M_A10_TO_Support.pdf PDF
FA820216R1000_______0004.pdf PDF
Question_set__10.docx DOCX document
Question_Set__9.docx DOCX document
FA820216R1000_______0003.pdf PDF
RFP_Attachment_2-Section_M_A10_TO_Support_13_June_2016.docx DOCX document
Question_Set__8.docx DOCX document
Question_Set__7.docx DOCX document
FA820216R1000_______0002.pdf PDF
RFP_Attachment_1-Section_L_A10_TO_Support_8_June_2016.docx DOCX document
Question_Set__6.docx DOCX document
38784STD-BV9a.dtd DTD file
38784STD-BV9a_releasenotes.doc DOC document
38784STD-BV9a_TDT.pdf PDF
38784STD-BV8a_scripts.zip ZIP file
isoentities.zip ZIP file
Question_Set__5.docx DOCX document
readme.txt TXT text file
Question_Set__4.docx DOCX document
RFP_Attachment_13-Labor_Category_Description.pdf PDF
83495C1CV9D0P1_TDT.pdf PDF
PLM_Data_Exchange_Specification_12-A10DOC-002_Appendix_Table_Fv0.5.xlsx XLSX spreadsheet
7700H-CV9D0P0_TDT.pdf PDF
readme.txt TXT text file
MIL-DTL-9977_Rev_M.pdf PDF
83495C1CV9D0P1.fosi —
7700H-CV9D0P05x11.fosi —
7700H-CV9D0P0_scripts.zip ZIP file
83495C1CV9D0P1_Release_Notes.docx DOCX document
38784STD-BV8a_scripts.zip ZIP file
7700H-CV9D0P0.fosi —
Show 40 more

Latest 50 of 105 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

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

Text version

TECHNICAL QUESTIONS

Amendment 5, Question Set 11

IAW TO 00-5-3, para 3.6.1, a completed (initial) TMCR for TO Sustainment only will be included in the solicitation (RFP). MIL-STD-1808/S1000D initial TMCR will be provided when awarding a task order for MIL-STD-1808/S1000D conversion, migration, sustainment and data management.

1- Can the government please provide a copy of the initial TMCR for this solicitation?

ANSWER: The Government no longer requires a TMCR for MIL-STD-1808/S1000D

Conversion as part of this solicitation. (L, M and PWS updated accordingly)

2- Can the government clarify the intent of Section L. para 4.4 and Section M, para 4.4;

3- Recommend the government remove the initial TMCR requirement from Sections

L&M.

4- Can the government provide a copy of the TMCR and TOLCMP Functional Guides?

ANSWER: The TOLCMP functional guide will be provided. See Attachment 19. However, this is not required for the accomplishment of the solicitation.

The Government no longer requires a TMCR for MIL-STD-1808/S1000D Conversion as part of this solicitation (L, M and PWS updated accordingly). There is no functional guide for a TMCR.

The initial TMCR for TO sustainment is provided. See Attachment 18.

5. Regarding Task 1, it states:

Convert ‘Sample Task 1’ into a Job Guide and SGML files IAW MIL-DTL-83495D. Be sure to include front matter data (Cover, Table of Contents, etc.). Add the following Distribution

Statement for the front cover.

The DTD provided is revision C.

ANSWER: The nomenclature of files within a Technical Manual Specifications and Standards

(TMSS) Digital Support Suite (DSS) may not match entirely with the nomenclature of the latest version of the applicable MIL-STD/PRF/DTL specification. This is because some updates to the specification do not drive an update to the Document Type Definition (DTD). See email screenshot below for response from TMSS program manager.

6. Regarding sample task 2, it states:

Convert ‘Sample Task 2” into a Flight Manual Checklist in SGML format per MIL-DTL-7700H and IAW additional requirement detailed below in section 2. Be sure to include front matter data

(Title, LEP, Table of Contents, etc.). Add the following Distribution Statement for the front cover.

MIL-DTL-7700H is incomplete without DTD38784STD-BV9.

ANSWER: The DTDs provided by TMSS include all their prerequisite DTDs inline and are parsable as a single, complete DTD with some minor modifications. There are comments in each

DTD file that describe those modifications, and we provided the modified DTDs in the solicitation.

See below for specific line numbers in DTDs for MIL-DTL-7700H where the prerequisites begin and end. NOTE: this applies to more than just Task 2.

See below for TMSS affirmation that the DTDs, as delivered in the DSS are "resolved”

(meaning, parsable on their own without additional DTDs).

The DTDs included are all resolved. So while each of the DSSs reference the 38784 DTD, the

DTD has already been resolved into the subset DTDs.

7. Regarding sample task 3, it states:

Convert ‘Sample Task 3” into a Digital Checklist in SGML format per MIL-PRF-9977M and

IAW additional requirement detailed below in section 2. Be sure to include front matter data

(Cover, Table of Contents, etc.).

The DTD provided is revision L.

ANSWER: Same answer as given above for the observation related to Task 1. The condition of potentially mismatched nomenclature applies to all TMSS DTDs, and will arise any time a specification revision doesn’t drive a change to the DTD. The TMSS DTD will bear the nomenclature of the MIL-STD/PRF/DTL current at the time the DTD was developed; the DTD will not be renamed within the DSS just to match a revision MIL-STD/PRF/DTL if that revision didn’t drive a change to the DTD.

8. Block 14 of the SF33 only has space for four (4) amendments and to date, there have been five (5). Please advise how are we indicate the appropriate number of amendments on the SF33?

ANSWER: Each amendment (SF30) requires the offeror to acknowledge receipt of this by completing Block 15. Section L, paragraph 3.1 has been updated accordingly. Please see

Attachment 1.

9. Block 3 of the amendments do not have an effective date indicated.

ANSWER: Block 3 does not include an effective date until contract award. The date of posting the RFP or amendment is the notional effective date.

10. We have been told Mr. Anderson is no longer the PCO for this effort however, the solicitation (Section L, paragraph 1.4) still indicates him as the PCO with Ms. Held as the

Buyer.

ANSWER: Paragraph 1.4 of Section L has been updated to list Ms. Cindy Chartier as the PCO.

Please see Attachment 1.

11. Section L, paragraph 1.4 of the solicitation indicates a due time of 1400MT but the

SF30 issued as Amendment 005 states 0900 AM MDT.

ANSWER: The due date has been extended and the time changed. Paragraph 1.4 of Section L has been updated to indicate a time of 1300 MT. Please see Attachment 1.

File details come from the government source that posted it. Updated .