Draft_RFP_QA_Responses_28Mar13.xls
XLS spreadsheet 78 KB Posted
- Attached to
- ESG DSIAC BCO Federal contract opportunity
- Solicitation number
- FA8075-12-R-0004
About this file
DSIAC BCO Draft RFP Compiled QandA Final 28Mar13
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| DSIAC_BCO_RFP_Q A_3Jun13.xls | XLS spreadsheet | |
| Amendment_0001_Final_4Jun13.doc | DOC document | |
| DSIAC_BCO_RFP_Q A_Format.xls | XLS spreadsheet | |
| DSIAC_BCO_RFP_10May13.doc | DOC document | |
| Notice_FedbizOpps_SB_Director.doc | DOC document | |
| DSIAC_PreSolicitation.doc | DOC document | |
| Draft_DSIAC_BCO_For_31Jan13.doc | DOC document | |
| RFP_Q A_Format.xls | XLS spreadsheet |
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
Sheet1
| DSIAC BCO RFP Q&A As of 28 March 2013 | |||
| # | Solicitation Section | Question/Comment | Response |
| 1 | PWS Section 4, para 4.1 | Section 4.1 (first paragraph, last sentence) references a graph with a notional schedule for Phase-in/Phase-out, and I can’t seem to find the graph. | The graph will be provided in the final RFP. |
| 2 | L1.10 | In reference to Paragraph L1.10 BUDGET PROFILE: “The projected Full Time Equivalents (FTE) profile for DSIAC is estimated to be 20 FTEs per year. This figure is an estimate derived through an integrated analysis of historical IAC data, current data, and future projections. This profile includes all FTEs associated with the transition, maintenance and operation of the IAC. The Government is providing this figure as an estimate only. “ Does this include all system matter experts (SMEs) required as full time staff to replace the SMEs in the “current” six Information Analysis Centers (IACs) that are being combined into DSIAC, and does the estimate include the “network of SMEs” and the “reach back” capability referred to in the draft RFP? | The FTE estimate was based on an estimate of the personnel who would be employees of the prime and its subcontractors, performing direct billable support on the contract. It is up to each offeror to decide how to account for the hours and cost of services provided by its network of SMEs or "reach back" resources. |
| 3 | General Question | Request for the latest government estimate of the annual funding profile to support the DSIAC BCO exclusive of funding for Core Analysis Tasks (CATs), which we understand to be customer funded (non-DTIC) and is exclusive of the cost estimate for this contract. This request is related to the question #1 and the FTE estimate in that the cost estimate for 20 FTEs; ISS development, operations, and maintenance; and other DSIAC BCO operations does not match the previously estimate of $5M per year for 6 years funding profile. | The information provided in the draft RFP is the only information that will be provided regarding the government's independent cost estimate. The estimate of 20 FTEs in RFP paragraph L.1.10 is the government's best estimate of DSIAC staffing requirements. CATs are customer-funded efforts that are conducted outside of the 20 FTEs estimated for the DTIC-funded requirements. |
| 4 | Section L & M | Request for clarification to the past performance relevancy requirement for the five requested past performance citations. As the criterion is written, it appears difficult for each and every past performance citation to contain the sub-elements of all four criteria: Operations Approach, Management, Information Support System and Cost (cost-type contracts) within the citation. Is the Government willing to evaluate past performances utilizing one or more criteria, aggregating across all submitted to show relevancy? | As stated in the RFP para. M3.1.3, "Relevance is defined by the degree of similarity between the Offeror’s current/past performance and the current DSIAC BCO requirement". The Government will evaluate all past performance information submitted by the offeror and assess its relevancy. The RFP does not state that the Government will only evaluate past performance citations that cover all criteria. |
| 5 | General Question | To assist in the submission, when and how does the Government plan to release a technical bidder’s library containing all relevant documents on the current IACs, and policies and procedures relevant to this procurement and the requirements? | Information needed by offerors to propose on this RFP will be provided either as an attachment to the RFP or as a document publicly accessible through a web URL that is cited in the RFP. |
| 6 | General Question | In reviewing the Sources Sought of March 2012 Questionnaire, Section 14 required a listing of scientific papers that each organization has authored in the last two years. Is it a requirement for the BCO Prime contractor to develop technical papers and technical area tasks, or is the function of the BCO primarily the management and day-to-day administrative operations of the IAC(s)? | The BCO is not primarily administrative in nature, but rather serves as DoD's center of technical expertise in the scope areas listed in the RFP. Authoring technical papers and performing technical core analysis tasks (not technical area tasks) are both requirements of the PWS. |
| 7 | Section B, Minimum and Maximum Values, pg 11 | What is the planned/budgeted maximum value of this contract? | The Government will not be releasing the independent estimate for this contract. However, the Government provided a projected Full Time Equivalents (FTE) profile for DSIAC, and estimated it to be 20 FTEs per year. This figure is an estimate derived through an integrated analysis of historical IAC data, current data, and future projections. |
| 8 | Section B, Minimum and Maximum Values, pg 11 | Clarification: What is the planned/budgeted contract value for CLINs 0001, 0002, and 0005? What is the planned/budgeted contact value for CLIN 0003? What is the planned/budgeted contract value for CLIN 0004? | The Government will not be releasing the independent cost estimate for CLINs 0001, 0002 and 0005. CLIN 0003 is $24M and CLIN 0004 is not separately priced. The $15M stated in Section B for CLIN 0003, will be corrected to read $24M in the RFP. |
| 9 | PWS, Section 1.4.1.1.2, para 2 | Are all the references to "DTIC Online" referring to DTIC Online Access Controlled (DOAC) or some other system that will be used by the warehouse company and/or the BCO? | There are three components to DTIC Online: a public DTIC Online, DTIC Online-Access Controlled (DOAC) and a classified DTIC Online. As referred to within this PWS, they are collectively referred to as "DTIC Online". |
| 10 | PWS, Section 1.4.1.1.4 b, para 4 | This paragraph mentions the data warehouse "delivering the document electronically to the DSIAC contractor using secure encrypted e-mail". Will this require the DSIAC contractor to have a CAC enabled e-mail system as used by DoD for encrypted files or will a commercial system be sufficient? | A CAC-enabled email system is not required. A commercial email system that is able to receive encrypted emails from the data warehouse contractor's commercial email system is sufficient. |
| 11 | PWS, Section 1.4.1.1.4 d | What is the expected "up" time for web services? | It is assumed by "web services" the requester was referring to the DSIAC website. There is no minimum established "up time" requirement in the RFP for the DSIAC website; it is expected to be available 24 hours/day, 7 days per week; however, it is understood that it may be occasionally taken down for routine maintenance, with advance notification made whenever possible. |
| 12 | PWS, Section 1.4.1.1.4 d | Is there a requirement for the contractor DSIAC network to be a stand-alone network within the contractor's network? | No, this is a decision to be made by the contractor. However, contractor workstations that will process classified information cannot be connected to the contractor's unclassified network, per NISPOM requirements. |
| 13 | PWS, Section 1.4.1.2, para 2 | At the point of award of DS TATs, the DSIAC contractor shall transition to interfacing with the DS TATs contractors. How do you see this interface during transition? How do you define the interface? | The DSIAC BCO contractor will interface with the incumbent contractors to transition the IAC Basic Center Operation. Simultaneously, the DSIAC BCO contractor will continue to interface with the incumbent contractors and then the follow on contract called DS TATs to primarily capture the TATs and STI contributions that will be accomplished according to the PWS, Section 1.4.1.2, paragraph 2. Also, please see question and answer #75. |
| 14 | Section C of the DRAFT RFP – Paragraph 1.4.1.2 – Information Analysis | The last paragraph ends with “It is estimated the two FTEs will be required to”. Could the Government provide the remaining information for that sentence and enumerate the tasks required of the two FTEs identified in the section? | This paragraph has been revised. See paragraph 1.4.1.2. |
| 15 | PWS, Section 1.4.1.2, para 3 | Is there a requirement for the DSIAC contractor network to be directly connected to the DoD network (NIPR)? Or via the WWW? | DSIAC contractor is not required to connect directly to the non-classified IP data network (NIPRnet). |
| 16 | PWS, Section 1.4.1.5.2, para 2 | Who makes up the DSIAC Steering Committee? | The participants have not yet been formally identified. |
| 17 | PWS, Section 1.4.1.3 | Will there be a formal process established for the TAT contractors to support (fund) DSIAC analysis and STI collection and evaluation activities related to these LARGE contracts or will this be covered under the BCO or CAT? | It is not anticipated that TAT contractors will fund BCO or CAT activities. |
| 18 | PWS Appendix 5-3_Master List of all DS Legacy KRs.xlsx | Would you identify what role or roles does each existing server play? (Directory Services, Database, Web Services, E-mail, Backup, etc.) | This information is proprietary to the incumbent contractors. The information provided in PWS Appendix 5.3 is intended only to give offerors an idea of the types of server hardware they might need to perform the PWS and the types and sizes of listserves and databases they will be working with. Each incumbent IAC contractor has configured its IT network differently and the applications, files and databases each contractor hosts on each of its servers, i.e., the role each server plays in its network, is particular to that contractor. There is no required or optimal configuration. The DSIAC contractor is free to set up its own network. The incumbent contractors' servers will not transition to the DSIAC contractor. |
| 19 | PWS Appendix 5-3_Master List of all DS Legacy KRs.xlsx | How many tables and rows are within the databases? The list provided is not consistent. Please provide a complete list of the tables and row for each database in order to provide a better cost estimate. | The estimated number of records (rows) listed in Appendix 5.3 for each database is for all of the database's tables combined. The typical database has between 10 - 50 columns. |
| 20 | PWS Appendix 5.3 Master List of All Legacy KRs | The CPIAC tab does not list the following legacy databases and manuals developed under Government funding: |
Rocket Motor Electronic Database (RMED) CPIA Rocket Motor Manual Vol. II (Confidential) Solid Propellant Database (SPD) CPIA Solid Propellant Manual Vol II (Confidential) Propellant and Explosives Ingredients Database (PEID) Air breathing Propulsion Manual Solid Rocket Motor Static Test Facilities Manual Liquid Propulsion Database (LPD) Chemical Propulsion Information Network (CPIN) Interface
| Please confirm that these legacy databases will be part of the transition inventory. | Appendix 5.3 is not intended to list all products produced by the legacy IACs at government expense, such as manuals. Those will be identified to DSIAC by the incumbent contractors during the transition period. The databases identified are JANNAF owned/funded databases. JANNAF support is not included in the scope of DSIAC so these databases will not transition to DSIAC. CPIN is not a database but rather is a login portal for all the other databases and it will not transition. | |||
| 21 | PWS, Section 1.6.3 | Search and Summary efforts: Will a SOW or subscription be required to perform search and summary efforts? | A SOW may or may not be required, depending on the nature of the search and summary effort. | |
| 22 | PWS, Section 5.2, DSIAC Combined total table, pg 49 | How many of the meetings and symposiums listed were funded by core and /or a TAT? | The table in Section 5.2 includes a column for trainings and meetings. For the combined total shown, it is estimated that approximately 60% were TAT-funded. This is just an historical estimate as DTIC does not compile these figures. | |
| 23 | PWS, Section 5.2, DSIAC Combined total table, pg 49 | How many request and man-hour per year were received by legacy contractors for models and data bases? | This figure is not available for any IAC except SURVIAC -- see the updated PWS in the final RFP, paragraph 1.4.1.2. The workload associated with handling models and databases for all IAC scope areas combined is captured in the estimated requirement of 20 FTE for the overall DSIAC contract. See RFP paragraph L.1.10. | |
| 24 | Clauses, Section 52.216-19 (b)(1) | Typo in sentence: "Any order for a single item in excess of $500,00.00;" What is the correct value ($50,000 or $500,000)? | Fill-In for 52.216-9 (b)(1) will read $500,000.00 | |
| 25 | Clauses H.14 Contractor's Phase-in and Phase-out/Transition, para (7) (a) v | What is the quantity of the Educational Courseware, electronic and physical storage? | The quantities of the incumbent contractors' physical materials to transition, and their physical storage requirements, have not yet been identified for each IAC. This will be finalized in the incumbent contractors' Phase-Out Plans. Electronic storage requirements are captured in PWS Appendix 5.3. See answer to Question # 13. | |
| 26 | Clauses H.14 Contractor's Phase-in and Phase-out/Transition, para (7) (a) v | What is the quantity of the Symposia Operations material, electronic and physical storage? | See answer to Question #25 | |
| 27 | PWS 1.10 & 1.4.1.2 | Will SIPRnet access be granted to the successful offeror beyond the SIPRnet node indicated at WPAFB? | No. | |
| 28 | PWS1.4.1.3.2.1 | Do any of the DTIC or existing IAC information system resources or databases require a CAC-card for access? | No, none of the IAC information resources or databases require a CAC-card for access, except for those involving the SIPRnet account to be furnished at Wright-Patterson Air Force Base. Personnel working at that location will be issued CAC cards. | |
| 29 | PWS1.4.1.3.2.1 | Does DTIC envision the BCO migrating to CAC-enabled systems? | No. | |
| 30 | PWS 1.3&PWS 1.4.1.1.3 | In PWS 1.3 it states “…the IAC will be responsible for participating in JANNAF events for which JANNAF is either a sponsor or attendee.” And, “The IAC will also be responsible for participating in the Military Sensing Symposium.” Yet in PWS 1.4.1.1.3, it indicates, “The contractor shall provide technical input to support scientific, technical, and DoD-related DSIAC management conferences, symposia, workshops, and other meetings. These functions shall include providing technical coordination and information services required to support and host the meetings of the DSIAC Executive Steering Committee and Program Review which will occur at least once a year.”. Please confirm there is a desire to, not only participate in JANNAF events and MSS, but to also provide technical coordination and information services to include hosting. | Services performed in direct support of JANNAF, such as meeting-related hosting, coordination, and information services, have been removed from the IAC program and are not a requirement for DSIAC to perform. Participating in JANNAF events, utilizing STI generated at JANNAF events that is made available to DSIAC, and interfacing with JANNAF on matters of mutual technical interest, are a requirement of the DSIAC PWS. With respect to the Military Sensing Symposium (MSS), the DSIAC PWS only requires the contractor to participate in MSS events, however DSIAC may elect to contribute to the events in other ways at its discretion (e.g., presenting technical papers, recommending topics, etc). | |
| 31 | PWS 1.4.1.2 | PWS 1.4.1.2 state, “It is expected DSIAC will send out approximately 20-25 classified (SECRET) model updates per week to users, and will be responsible for confirming in JPAS that recipients have the appropriate clearance needed to receive the update. “ Please confirm the approximate number of classified (SECRET) model updates per week. | The information requested in this question is as stated in the RFP (as cited by the questioner in the body of the question -- 20 - 25 updates per week). However please see updated PWS paragraph 1.4.1.2 in the final RFP which addresses survivability/vulnerability model and non-model related work to be performed at Wright-Patterson Air Force Base. | |
| 32 | Section B (MINIMUM AND MAXIMUM VALUES) | Section B, Minimum and Maximum Values Heading indicates “*The total of all Core Analysis Task Orders issued to the contract holder under the DSIAC BCO IDIQ contract shall not exceed the maximum award amount of $15M. The amount proposed for CLIN 0001, 0002, and 0005 and the maximum $24M for CLIN 0003 will establish the maximum ceiling value for the awarded contract. The Government reserves the right to move values between CLINs.” Please clarify whether the CAT ceiling is $15M or $24M? | The CAT ceiling for CLIN 0003 will be $24M in the RFP. Please see answer to question #8. | |
| 33 | PWS 1.10 | Please confirm that all office equipment and work space will be GFE for 2 FTEs to be working at WPAFB per PWS 1.10. If it will be GFE, please confirm it will be provided upon contract award. | All office equipment and work space for personnel to perform at WPAFB will be government-furnished. See updated PWS paragraph 1.4.1.2 in the final RFP. | |
| 34 | PWS 1.10 | Please confirm the 20 FTE estimate per year includes the two SMEs to be located at WPAFB per PWS 1.10. | Yes. | |
| 35 | Within Section C of the DRAFT RFP – Paragraph 1.5 – Service Charge System | We assume that reimbursement for Core Area Tasks garnered under the Service Charge System will NOT apply to the maximum ceiling for CATs. Could the Government please confirm that the assumption is correct? | Products and services funded under the Service Charge System do not apply to the $24M maximum ceiling for core analysis tasks (CATs). | |
| 36 | Section 5.2, pages 43-49 | In this section the Government has provided historical data for each legacy IAC referencing the number of Technical Inquiries for each. It is our understanding the CAT concept is new and did not exist under the legacy contracts. Would it be possible to get clarification what percentage of these inquiries were funded (Extended and Search and Summary) versus unfunded (Basic)? Could the Government include an estimate, based upon historical data and CAT definition in the draft RFP, on how many CATS the DSIAC BCO could expect within a 12 month period? | With respect to inquiries, DTIC does not collect data on the percentage of technical inquiries that are funded vs. without charge. However, the Government estimates that the vast majority of historical inquiry workload shown in the draft RFP Table 5.2 were the four-hour "without charge" type inquiries. Regarding CATs, the RFP ceiling amount of $24M over six years is DTIC's best estimate of the magnitude of CAT ordering. On the other two IAC BCO-only contracts that utilized CATs, the average ceiling dollar value of a CAT was $211,000 (with a one year CAT period of performance). On the two BCO contracts awarded to date (DACS and now CSIAC), three - four CATs have been issued per year. | |
| 37 | Section 5.2, pages 43-49 | In reference to the historical data charts provided, could the Government provide clarity on the metric “number of training/meetings? For example, does it mean the number of meetings where the BCO had someone in attendance, or does it mean the BCO actually hosted and disseminated information/presented at the meeting? | This metric refers only to meetings/trainings where the BCO either hosted the meeting or served as a sponsor or contributor. | |
| 38 | Section H.13 Key Contractor Personnel, page 61 | It mentions key personnel, but only identifies the Director of the DSIAC BCO as key, are there any other gov identified key personnel? | No. | |
| 39 | Section L1.10 Budget Profile, page 118 | It refers to the $24M ceiling for CATS over the period of performance. Does this $24M include dollars spend by customers for Extended and Search and Summary technical inquiries as well? | See response to question #8 and question #35. | |
| 40 | Section H.3, page 58 | Could the Government confirm that the OCI restrictions apply only to prime contractors and not the subcontractors? | The firm OCI restriction stated in clause H3 only applies to BCO prime contractors. However, if an actual, appearance of, or potential OCI arises at any time, pre or post-award, for either the prime contractor or a BCO subcontractor, that OCI will have to be disclosed to the Contracting Officer. At that point, the CO may request an OCI mitigation plan from the concerned party and may determine, after evaluating the mitigation plan, that the OCI is unmitigatable. | |
| 41 | Section H.3, page 58 | In previous RFPs for similar work the Government provided guidance on the Organizational Conflicts of Interests related to the TAT work. Will there be an OCI restriction related to Contractors pursuing work under the TAT IDIQ vehicles? | The DSIAC BCO OCI clause H3 is identical to the ones used on the similar CSIAC contract and HDIAC RFP. The DS TATs contract will contain an appropriate OCI clause, similar to the H3 clause contained in the Homeland Defense TATs RFP "FA8075-12-R-0002", posted at www.fbo.gov. The DSIAC OCI restriction in clause H3 prevents the BCO prime contractor from performing as either a prime or subcontractor on the DS TATs contract. There is no restriction for a BCO prime or subcontractor to perform work on the other, non-Defense Systems, TAT IDIQs. | |
| 42 | Section H.14, page 61 | The Statement of Work makes mention in H.14 of contractors needing to develop a transition out plan, however no CLIN exists in Schedule B for such. Will the Government consider adding a separate CLIN to Schedule B for Phase Out costs/transition as well as consider providing a plug figure for such for the purposes of standardizing evaluation between offerors since the transition out plan would depend heavily on whomever the successor contractor is several years from today and cannot possibly be known at this time? | The phase out will not be priced in the proposal. The Phase-Out will be paid for by DTIC using the CAT CLIN 0003. A transition phase-out plan is not required at this time. | |
| 43 | PWS Section 1.1 | There is a reference to the military sensing IAC identified as MSIAC--don't you mean SENSIAC? | Yes, the reference should be for SENSIAC. This will be corrected in the final RFP. | |
| 44 | PWS Section 1.6.1 | Are CATS to be accomplished using RMS or is there a simpler process? | The CATS will utilize the DTIC Requirements Management System (RMS) process. | |
| 45 | PWS Section 1.6.1 | Is there any history of CATS on CSIAC? | The CSIAC BCO has not had one full year of performance to date. At this time Four CATs have been issued since the CSIAC BCO contract was awarded. | |
| 46 | General Question | To what extent have the legacy IACs partnered with existing conferences? | The major organizations that the defense systems IACs have partnered with JANNAF and MSS to host conferences. The legacy IACs' respective relationships with event hosting organizations as well as their participation in such events are described in the materials on their respective websites. | |
| 47 | General Question | Have legacy IACs coordinated to determine conference attendance, or were decisions made separately? | The legacy IACs establish conference attendance goals and projections only for those conferences they host. For other conferences that an IAC participates in or otherwise attends but does not host, the conference attendance decisions are made by the sponsoring organizations. The IACs' estimates of event attendees that they have reported to DTIC as a metric have been based on the IACs' own best estimates, or may have been obtained from the sponsors of the events. | |
| 48 | Section B | Will an official IAC transition schedule (with dates) be provided to assist pricing of CLINs 0001-0001AF? | All Offerors will provide their cost data based on assumed start date of the contract provided for in the RFP. See RFP L5.1. Additionally, the final RFP will contain a notional transition schedule. These dates will be subject to change depending on the actual award date of DSIAC. However, regardless of the DSIAC award date, the plan is for each legacy incumbent IAC's transition period (phase-out period) to DSIAC to have a maximum period of performance of 90 days. All legacy IACs' phase-out periods will start within the same 90 day window after award of DSIAC. All legacy IACs' phase-out periods will end no later than 180 days after award of DSIAC. The legacy IACs' individual 90 day transition periods will be staggered within this 180 day window. | |
| 49 | PWS Section 1.1 | Will a WBS of transition activities between the legacy IACs and incoming contractor be released? | No work breakdown structure (WBS) will be created by DTIC. The final DSIAC RFP contains an updated H.14 Transition clause which is essentially the same as the clause that the legacy IACs' contracts will include. This clause provides an overview listing of all anticipated transition activities. The legacy IACs will be responsible for detailing their phase-out activities which will be included in their respective transition plans. These plans will be shared with the DSIAC contractor upon award of DSIAC to allow for coordination and fine tuning of DSIAC's phase-in plan. | |
| 50 | PWS Section 1.1 | Will a Transition Plan between the BCO and TAT organization be required? | No. | |
| 51 | PWS Section 1.3 | What is the process for identifying and establishing 'emerging threat' requirements within the IAC SOW? | The IAC performance work statement (PWS) will not establish/identify emerging threats nor detail specific requirements for how DSIAC should consider those threats in performing the contract. DSIAC is required to understand and stay abreast of the emerging threat environment -- this is one of the requirements the contractor will be paid to perform. DSIAC is required to maintain awareness of emerging threats by utilizing the resources at its disposal (its subject matter expert network, incoming inquiries, relevant STI, conference proceedings, DoD publications and advisories, etc.). | |
| 52 | PWS Section 1.3 | For dissemination purposes, does a DoD stakeholder list exist? | No, there is no master list of DoD stakeholders. | |
| 53 | PWS Section 1.3 | Is there a process for identifying duplicative STI and how it impacts new inquiries? | A primary purpose of the IAC program is to reduce creation of duplicative STI within DoD by sharing and re-utilizing existing STI. DSIAC will be responsible for disseminating STI that is most relevant and useful to its customer base and will need to take into account trends and patterns in inquiries when determining which topics are most relevant. In addition, when DSIAC performs literature searches in advance of new DS TATs being awarded, DSIAC will identify existing STI relevant to that TAT. This will reveal to the TAT contractor any overlap or duplication between existing STI and the STI deliverables called for in the TAT performance work statement. | |
| 54 | PWS Section 1.3 | Please further expand on the relationship between DSIAC and JANNAF. What are the JANNAF requirements for DSIAC? | See answer to Question #30. | |
| 55 | PWS Section 1.3 | When will the decision be made regarding the BCO Task Order Procurement Process (annually, semi-annual, or quarterly TO). | The DSIAC BCO task order will be awarded once the contract is awarded and align with the structure of the contract. Base Year for 2 years and 2 options for 2 years each. | |
| 56 | PWS Section 1.3 | What legacy TAT access will the BCO possess? | The BCO should not need access to the legacy TAT delivery orders themselves. Access to STI generated under all TATs will be available to DSIAC through DTIC Online, to the extent that distribution statements allow access. In addition, summary information about the scope of some TATs, organized by IAC, is available on DoD Techipedia's IAC subsite. | |
| 57 | PWS Section 1.3 | Please provide examples of 'international organizations' in which the IACs have historically participated. | The international organizations that the IACs have interfaced with are too numerous to list. Some can be found by searching through the materials on the IACs' individual websites or conducting a search in DTIC Online. PWS paragraph 1.3 addresses the requirement for DSIAC to maintain awareness of the RDT&E activities of international organizations in which the U.S. Government is a member or participant. A few examples of such organizations are the North Atlantic Treaty Organization (NATO), the International Atomic Energy Agency, the World Health Organization, the Artic Council and the International Telecommunication Union. | |
| 58 | PWS Section 1.3 | What are the limitations on IAC research (vice 'doctrine, tactics, or plans') for foreign governments and FMS partners? | Limitations on IAC research for, and exchanges with foreign governments are addressed in the directives and references listed in Section J, Attachment 2. | |
| 59 | PWS Section 1.4.1 | What is the expected relationship between DSIAC and the other IACs (HDIAC and CSIAC)? | They will be expected to engage with each other on science and technology topics of mutual interest. | |
| 60 | PWS Section 1.4.1.1.3 | What are the facility requirements for hosting the DSIAC Executive Steering Committee and Program Review? | A conference room that can hold up to 40 people with equipment such as a laptop projector, internet connectivity and conference calling capability are sufficient. Specific location of individual program reviews and steering committee meetings will be coordinated on a case-by-case basis, and may be conducted at a government site. | |
| 61 | PWS Section 1.4.1.1.4.b | Will DSIAC be restricted in the number of data requests to the data warehouse company? | No. | |
| 62 | PWS Section 1.4.1.1.4.b | Will DSIAC be restricted in the dissemination of STI from the data warehouse company? | Yes, all STI contains a distribution statement which DSIAC will need to adhere to when disseminating the STI. | |
| 63 | PWS Section 1.4.1.3.1.1 | Will the DSIAC contractor manage, or only interface with the DTIC Online STI database? | DSIAC will not manage DTIC Online but will be using it to upload STI into the database, as well as search it and retrieve documents from it. | |
| 64 | PWS Section 1.4.1.3.2.1 | Will the BCO be responsible for identification and removal of duplicative STI between the DTIC Online STI database and the IAC database? | DTIC Online is the master database of DTIC for STI. Databases transferred from the legacy incumbent IAC contractors to DSIAC may contain some STI that is duplicative of STI in DTIC Online. DSIAC may delete this duplicative STI in its own databases at its discretion. STI that is not duplicative should be uploaded to DTIC Online. DSIAC will not be authorized to delete materials from DTIC Online. | |
| 65 | PWS Section 1.4.1.3.2.3.a | Will the BCO have access to legacy IAC user information? | Yes, this information will be transferred from the legacy IACs during their transition periods. | |
| 66 | PWS Section 1.4.1.4.1 | Who will be responsible for pricing/cost decisions for Extended Tech Inquiries and Search & Summary inquiries? | DSIAC contractor will determine price based on specific requirements and associated costs. | |
| 67 | PWS Section 1.4.1.5.1 | What is the relationship between ASD(R&E) and DSIAC? What data or program review requirements exist? | As stated in the RFP, DTIC falls under ASD (R&E). DSIAC will not have a direct relationship with ASD (R&E). All reviews and oversight of DSIAC will occur through the DTIC IAC PMO. | |
| 68 | PWS Section 1.4.1.5.2 | How will the user estimate 'dollar savings' as a measure of feedback? | DTIC does not provide any specific guidance to users on how to calculate dollar savings. This is at the user's discretion. | |
| 69 | PWS Section 1.6.1 | Does DSIAC have the ability to charge for external education and training activities? | Yes. | |
| 70 | H-14 | "The government requires the submission of all financial data for all TATs performed on the contract." - Will all legacy TAT financial data be delivered to the incoming DSIAC contractor? | This clause will be updated in the final RFP. The requirement to transition legacy TAT financial data to the incoming DSIAC contractor has been removed. | |
| 71 | H-14 | Please define the members, requirements, and meeting frequency of the Steering Committee? | See the answer to Question 16. As stated in the RFP, the Executive Steering Committee will meet at least once per year. See Section J, Exhibit A, CDRL 0008. | |
| 72 | H-14 | How is GFE to be separated between CAT and TAT. | TATs will not be performed on this contract. DSIAC will not be receiving government furnished equipment for TATs. | |
| 73 | Sect. B | Regarding the transition period CLINs, almost certainly one of the |
transitions will be more difficult than anticipated, which would lead to a loss or overrun. If the transitions were combined into one CLIN then there is the potential for the contractor to make up for any
| difficult transition on one that may go easier than anticipated. Would you consider combining them into one CLIN? | To provide flexibility to the program, the 6 Transition Phase-In CLINs will be combined into 1 Transition Phase-In CLIN with a Period of Performance of 180 days in the final RFP. | ||
| 74 | Sect. B | CLIN five also seems unneccesarily complex with all the one month | |
| extensions. Couldn't extensions be handled later if necessary? | The Government may require continued performance of services and therefore made the determination to include the 52.217-8 clause via separate monthly CLINs for 6 months. | ||
| 75 | PWS para. 1.4.1.1. | There is mention of TAT contributions and producing STI . In my understanding the MAC contractor would be responsible for producing the STI and the BCO only capturing the STI already produced. There are various terms used throughout such as collaborate or interface with the MAC contractor. That seems very confusing. Furthermore any confusion in roles here could lead to a very large open ended work load on the BCO. | |
| I would suggest that you prepare an example of a TAT history from inception to completion and trace through what the BCO and MAC roles are and are NOT toward the ultimate goal of producing STI and capturing it for DTIC Online. That would clarify the respective roles and avoid potential problems down stream. | The Section J, Attachment 5, "CAT SOP" provides details on the BCO and MAC roles. So far, no serious problems have been encountered between BCO and MAC contractors. Also, please see question and answer #13. | ||
| 76 | PWS para. 1.3 | There are several mentions of relations with JANNAF and Military sensing |
communities, which are fine and highlight the importance of these organizations to DSIAC. I would hope that JASP , JCAT and JTCG/ME
| should also be added as important interface organizations for DSIAC. | The final RFP's identification of major sponsoring organizations of the defense systems legacy IACs will be updated. Those are considered to be JANNAF, MSS, the Jt. Aircraft Survivability Program Office (JASPO) and the Jt. Technical Coordination Group for Munitions Effectiveness (JTCG/ME). | |||
| 77 | PWS para. 1.6.1(3) | Can the total ceiling for each Core Analysis Tasks (CATs) order be increased from $500,000 to $1,000,000. Would provide more flexibility in meeting our limitation on subcontracting. | Yes. The plan is to increase the restriction from $500K to $1M based on approval for this change. |
Sheet2
Sheet3
File details come from the government source that posted it. Updated .