Responses_to_Industry_RFP_Questions__1.xlsx
XLSX spreadsheet 66 KB Posted
- Attached to
- Eastern Western Operational Communications Services (EWOCS) Federal contract opportunity
- Solicitation number
- FA2521-19-R-A018
About this file
This notice provides an updated solicitation number for the Eastern Western Operational Communications Services (EWOCS) procurement. The solicitation seeks operational communications services for the 45th Space Wing and 30th Space Wing.
The solicitation number has changed from FA2521-18-R0029 to FA2521-19-R-A018. All previous information related to sources sought, requests for information, industry days, and draft documents can be found under the old number. Meanwhile, the updated draft request for proposals has been posted to this announcement under the new number.
This acquisition is a total small business set-aside. The final RFP is anticipated for release on or around August 30, 2019. The procurement will provide operational communications services for the 45th and 30th Space Wings at Cape Canaveral Air Force Station, Patrick Air Force Base, Vandenberg Air Force Base, and associated geographically separated units.
Responses to Industry RFP Questions #1
View the file
Other files for this federal contract opportunity
Show all 40
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
Questions
| # | Document | Page # | Section | Quote of Section in Question | Question or Clarification | Answers | |
| 1 | EWOCS Draft PWS | 3 | |||||
| 5 | 1.0 | ||||||
| 1.6 | "While some communications services performed for various units associated with the ER and WR remain on other contracts or are performed by government employees, EWOCS is intended to consolidate as much as reasonably possible and legally allowable." and "The Contractor will interface with ESD, NOS and launch mission helpdesk. Helpdesks will be physically located at both wings" | If it is the intent of the Government to consolidate as much as possible, would the Government reconsider that helpdesks by physically located at both wings? Not all tiers of help desk need to be physically located in the same place to effectively perform their duties. | As stated in the PWS, the Government has a requirement that helpdesks will be physically located at both wings. | ||||
| 2 | EWOCS Draft PWS | 4 | 1.3.2 | " Contractor must be able to integrate with Air Force Network Operations (AFNETOPS) and provide network update and software configuration, anomaly tracking, system restoration, and response to Help Desk inquiries." | What are the prerequisites of integrating with AFNETOPS? Will a description of the current AFNETOPS system's capabilities be provided? | Requirement has been removed from the PWS. | |
| 3 | EWOCS Draft PWS | 5 | 1.5 | Various terminology has been used within ER and WR to describe mission support communications and mission communications. While there is a distinction as defined below, the intent of the EWOCS effort is to provide voice, data and video communications services regardless of the mission or mission support labels. | Currently, mission support communications and mission communications are provided through multiple contracts including ROS and LISC. If any current contract will not be fully superseded by EWOCS, where is the new boundary (patch panel, cable, etc.) between the base backbone and the end user equipment? What end user equipment, sites, or assets are excluded from EWOCS, i.e., antennas, radars, telescopes, etc.? | EWOCS responsibilities are identified in Appendix C (Comm Systems and Services Matrix). Any in-scope future requirements could be on-ramped through Task Orders during the life of the contract. | |
| 4 | EWOCS Draft PWS | 6 | 2.0 | "Site Observation, … Warfighter Topside Camera system,…" | These items do not appear to be part of the scope in the PWS. Could the Government please clarify where these should appear within the PWS? | The topside camera system supports MDA with video from all 5 MDA LFs with display in Bldg 1768 and Bldg 6510. (Para ref 3.12.1.) Paragraph 2.0 was adjusted for clarification. | |
| 5 | EWOCS Draft PWS | 6 | 2.0 | "To ensure performance of the mission, the contractor shall have a contingency plan to maintain full performance of services in accordance with this PWS in the event of work stoppages or labor strikes" | This plan does not appear in the CDRLs. Is this a required delivery under the PWS? If so, please update the CDRLs to include this plan. | We require contingencies be addressed in your overall program management plan. | |
| 6 | EWOCS Draft PWS | 7 | 2.1.1 | "The PD and Deputy PD must also have authority to sign and execute contractual actions such as contract modifications and task orders." | Contractual signature authority is not part of a typical Program Managers job function. Similar to the Government, contractual authority rests with personnel designated within a company who have the legal training and specialization in contractual matters. Suggest the Government remove the word "sign" from this sentence. | There must be personnel designated with the authority to sign and execute contractual actions such as modifications and Task Orders at both 45 SW and 30 SW. | |
| 7 | EWOCS Draft PWS | 7 | 2.1.3 | "Provide on day one of the contract performance, a government approved, secure, fully operational information data management system …." | Please define if "government approved" indicates any government agency? If not, then please provide understanding as to how offerors would get approval prior to contract award to be ready on day one of contract award. | This requirement has been modified for clarity and consolidated under para 2.7.1., Data Management. The Government approval is comprised of 45 SW, 30 SW and MDA representatives. | |
| 8 | EWOCS Draft PWS | 7 | 2.1.3 | "Provide on day one of the contract performance, a government approved, secure, fully operational information data management system …." | If a system is to be provided on Day One of contract award does the Government intend for the system to be company proprietary? This requirement would require development of the system precontract award to be ready for a day one provision of a system that is fully operational. Suggest the Government change this wording to "Provide for Government approval, by the end of transition period, a fully ..." | The system would not be company proprietary. It will belong to the Government. See PWS 2.7.1., Data Management. The Contractor shall provide a fully operational IDMS inclusive of all the requirements identied in the PWS within 9 months of full performance. | |
| 9 | EWOCS Draft PWS | 7 | 2.1.3 | "Provide on day one of the contract performance, a government approved, secure, fully operational information data management system …." | Meeting this requirement would indicate that contractors are providing an inhouse-developed product that would be provided for contract with Government-use rights. It is the offeror's understanding that the DoD and in particular the Air Force discourages the use of proprietary software since it ties the Government to a specific tool forcing an inherent advantage to the company who owns it for future procurements. Would the Government consider rewording this to require a system be developed and provided to the Government by the end of the transition period? | Yes. The Government does not believe a fully operational IDMS can be developed and fielded during transition. | |
| 10 | EWOCS Draft PWS | 7 | 2.1.3 | "Provide on day one of the contract performance, a government approved, secure, fully operational information data management system …." | Is there a system currently in use that is a preferred tool that is available for purchase and does not come from the incumbent? An incumbent tool may present a conflict of interest when it comes to delivering and implementing the tool in a timely manner. If the Government prefers the use of the incumbent tool, it is suggested that they purchase this tool and provide it GFP to the offerors to facilitate a fair competition. | The system that will be available from ROS can be modified by the EWOCS contractor for use during development of the new system. The EWOCS system would not be company proprietary. It will belong to the Government. Para 2.1.3 has been rewritten as 2.7.1. | |
| 11 | EWOCS Draft PWS | 7 | 2.1.3 | "Provide on day one of the contract performance, a government approved, secure, fully operational information data management system which shall include, but not be limited to: tracking programs supported, services provided, maintenance activities, actual labor hours, material costs, special projects, work control, quality control, teaming arrangements, property management, and contract direct costs, configuration management, and other areas where the program office requires visibility." | What level of security is required? Is this intended to be 1 system (as implied) that does all the things listed? | The Government would like this to integrate all the components listed in one system. Access will be granted to only those users identified by the Government (Restricted Access). | |
| 12 | EWOCS Draft PWS | 8 | |||||
| 39 | 2.1.6.3, 2.1.6.4 | ||||||
| 3.5.15 | "Experience and qualifications are in the PWS and contractor shall ensure qualified workforce to meet requirements. Certification of work being performed must be in compliance with DoD 8140.01 and DoD 8570.0-M." | What are the certification types/levels required for work execution? | System administrators must be certified within 18 months of performance start in the functional areas of their responsibilities. However, certification in Security Plus is required for (to include but not limited to) system administrators and Client Service Technicians on Day 1 of the contract. | ||||
| 13 | EWOCS Draft PWS | 8 | 2.1.6.3 | "Experience and qualifications are in the PWS and contractor shall ensure qualified workforce to meet requirements." | Are there position descriptions to be included with the solicitation? If not, suggest this wording be changed to "Contractor shall ensure qualified workforce to meet PWS requirements." | The labor descriptions will be included with the solicitation. | |
| 14 | EWOCS Draft PWS | 10 | 2.2.17 | Conduct operational tours with briefings and provide technical orientation and familiarization briefings when requested by the government. Include a short briefing on any radiation hazards or other items that pose a threat to human safety when applicable. | How many tours/briefs can we expected will need to be conducted monthly/yearly? | 12 +/-2 tours and briefs each for 45SW and 30SW are expected per year. | |
| 15 | EWOCS Draft PWS | 11 | 2.3.6 | "If the contractor submits a TOP for consideration, proposals will be evaluated on the basis of submitted information; in no event shall the equitable adjustment exceed the limitations established." | Request clarification on what established "limitations" are in this context? | The limitation established by the proposed negotiated price. | |
| 16 | EWOCS Draft PWS | 11 | 2.3.6 | "Task Order Proposals should take into account separate project management labor and not also apply project charges to the Communications Services CLIN." | Offeror assumes this means that Task Order Project Management should be priced and tracked separately and not added to the respective ER or WR Communication Services CLINs. Is this a correct assumption? | Yes, that is the correct assumption. | |
| 17 | EWOCS Draft PWS | 12 | 2.3.8 | "Approved Forward Price Rates (FPRs) shall be used to price and negotiate TOR costs." | Many small business entities do not get Approved Forward Pricing Rates from DCAA. Instead, they get what is called approved "Provisional Billing Rates". Suggest that this sentence be deleted from this paragraph. | Provisional Billing Rates have been added to the paragraph. | |
| 18 | EWOCS Draft PWS | 12 | 2.4.3 | "The Contractor shall ensure that the transitional change management process does not create a constructive change for the contract." | Could the Government please clarify, by example, the intent of this sentence? | The contractor cannot add or remove items or processes which affect the overall intent and functionality of the contract. | |
| 19 | EWOCS Draft PWS | 13 | 2.4.10 | "Submit a plan for day one operational implementation of an integrated data management system to the Government within 60 days of contract start" | This sentence is confusing. Are we submitting a plan on day one of contract with the implementation of an integrated data management system within 60 days of contract start? This requirement appears to be at odds with the requirements of 2.1.3. | Statements in the PWS have been modified to clarify. | |
| 20 | EWOCS Draft PWS | 13 | 2.4.12 | "Ensure all legacy data files as noted in the information data management system description are transferred and made available to the Government." | For pricing purposes, will the Government please provide a listing of all legacy data and their respective data formats. We request these data files be included on the GFP list. | The existing Fileshare data from ROS and CLOIS include, but are not limited to PDF, MS Word, MS Powerpoint, MS Excell spreadsheets, and VISIO drawings. | |
| 21 | EWOCS Draft PWS | 13 | 2.4.13 | "Implement an interim plan for all EWOCS managed data, including legacy data." | Offeror assumes that it has a system currently in place that performs the duties as described in the PWS. Will the Government provide access to this system via GFP for the period of phase-in, if necessary? | Yes. The existing Fileshare data will be available. | |
| 22 | EWOCS Draft PWS | 13 | 2.4.19 | "2.4.19. Submit a Government Property Management Plan to the GPA for review within 90 days of award to determine adequacy." | Should this Reference CDRL A015? | Yes, it has been referenced. | |
| 23 | EWOCS Draft PWS | 16 | 2.6.6 | "Implement a cost accounting system with flexibility to accommodate contract CLIN growth." | Please clarify the meaning of cost accounting system as it pertains to all of Section 2.6.6. Are you referring to systems that meet the DCAA-approved cost accounting standards? If so, the workscope associated with these requirements would be an indirect cost and not part of the PWS. If put within the PWS, then we would need to provide pricing to comply with this requirement. Suggest your remove the term cost accounting system and include instead "financial reporting system". | Implement a cost accoutning system that is flexible so that CLIN growth can be accomodated. | |
| 24 | EWOCS Draft PWS | 16 | 2.6.6.4 | "Perform within an economy of scope and maintain a minimum efficient scale for contract work based on the acquisition budget baseline as allocated by the Government." | Could the Government please clarify this requirement? | PWS has been modified for clarity. | |
| 25 | EWOCS Draft PWS | 16 | 2.6.6.4 | "Perform within an economy of scope and maintain a minimum efficient scale for contract work based on the acquisition budget baseline as allocated by the Government." | Is the Government going to provide the "acquisition budget baseline" allocation for the proposal or is this something we receiving at contract award? | PWS has been modified for clarity. The Government doesn't intend on releasing the acquisition budget. | |
| 26 | EWOCS Draft PWS | 16 | 2.6.6.5 | "Provide computer system support including hardware and software necessary to host the contractor’s accounting system." | Once this appears in the PWS, the offerors must price this system as a direct cost. Suggest removal of this subsection or addition to the GFP List. | The accounting system is based upon the offeror's technical solution. | |
| 27 | EWOCS Draft PWS | 18 | 2.7.7 | "Use the data management system to store information related to the following areas, at a minimum: CWBS; O&M data and procedures; metrics and performance reporting; work order management (or interface to system); quality management; financial reports; property and supply management; training management; safety management; CDRL reporting; environmental database and reporting; project status reports; status of communication systems that are supporting launches; maintenance schedules; and system manuals and maintenance procedures." | Is this data management system in addition to or part of the information data management system addressed in Section 2.1.3? | This data management system is part of the IDMS addressed in PWS para 2.1.3. | |
| 28 | EWOCS Draft PWS | 19 | 2.8.2 | "At a minimum, the prime contractor will be appraised by the Government at ISO 9001:2008 or ISO/IEC 20000 or Capability Maturity Model Integration (CMMI) Development Level 3 (or higher) using the Software Engineering Institute’s (SEI’s) Standard CMMI Appraisal Method for Process Improvement (SCAMPI)." | In section 2.8.1.1 the Government requires contractors to maintain a QMS that complies with 9001:2015 or equivalent. In this Section the Government references 9001:2008. For consistency, suggest the Government change this requirement to 9001:2015. | PWS para 2.8.2. has been changed to state 9001:2015. | |
| 29 | EWOCS Draft PWS | 19 | 2.8.2 | "At a minimum, the prime contractor will be appraised by the Government at ISO 9001:2008 or ISO/IEC 20000 or Capability Maturity Model Integration (CMMI) Development Level 3 (or higher) using the Software Engineering Institute’s (SEI’s) Standard CMMI Appraisal Method for Process Improvement (SCAMPI)." | Please clarify the meaning of the Government appraising the prime contractor for these standards and models. Normally, contractors receive their compliance or maturity level from independent third party authorized assessors. | PWS para 2.8.2. has been modified for clarity. | |
| 30 | EWOCS Draft PWS | 19 | 2.8.2 | "Formal certifications are accepted, but not required. Compliance with ISO or CMMI Level 3 processes is required." | Could the Government please identify all of the ISO Standards that apply to this contract aside from 9001 and 20000? For example, does 27001 also apply? | Only ISO 9001:2015 or ISO/IEC 20000 is required. | |
| 31 | EWOCS Draft PWS | 19 | 2.8.2 | "At a minimum, the prime contractor will be appraised by the Government at ISO 9001:2008 or ISO/IEC 20000 or Capability Maturity Model Integration (CMMI) Development Level 3 (or higher) using the Software Engineering Institute’s (SEI’s) Standard CMMI Appraisal Method for Process Improvement (SCAMPI)." | The PWS requires primarily services function not development. It is unclear as to why a CMMI Maturity Level 3 is necessary for performance. Instead, it is suggested that the Government add CMMI for Services at a minimum of Maturity Level 3 to ensure standardized service provision. | CMMI only applies to PWS Sections 3.11 and 3.12. | |
| 32 | EWOCS Draft PWS | 19 | 2.8.2 | "Formal certifications are accepted, but not required. Compliance with ISO or CMMI Level 3 processes is required." | Offeror's experience shows that in order to comply with ISO or CMMI the contractor should already be practicing at that level. Suggest that the formal certification to provide the Government with assurance of quality performance. | CMMI only applies to PWS Sections 3.11 and 3.12. Formal certifications are accepted, but not required. | |
| 33 | EWOCS Draft PWS | 20 | 2.8.2 | "In addition, small business companion contract awardees must comply with the same quality process requirements." | Please define "companion contract". | This sentence has been removed. | |
| 34 | EWOCS Draft PWS | 20 | 2.9.2 | "If removal and relocation of equipment and material is necessary, the contractor shall be responsible for disposal and shall comply with all applicable AF and industry rules and regulations." | For the purposes of this sentence, is removal and relocation of equipment always for disposal or could relocation be a move to another location that must be tracked? | It is not always for disposal. It can be moved to another location. PWS para has been changed to read, "If disposal or relocation of equipment and material is necessary, the contractor shall be responsible for disposal or tracking of that equipment, and shall comply with all applicable AF and industry rules and regulations." | |
| 35 | EWOCS Draft PWS | 21 | 2.9.2.1 | "The data fields required for MDA reporting are listed in Data Item Description (DID) DI-MGMT-80441C, “Government Property Inventory Report.” (A015, A016, M004)" | CDRL M004 not included in CDRL list. | Need to delete CDRL M004 from the list. Need to confirm with Stuart on A015. | |
| 36 | EWOCS Draft PWS | 22 | 2.9.3 | "For 30 SW and MDA transportation needs, the contractor shall use the Vandenberg AFB (VAFB) Transportation Management Office (TMO) to ship and receive freight to and from VAFB to the fullest extent possible." | Would the Government please identify how the 45th Space Wing's transportation needs should be handled? | PWS para has been updated. | |
| 37 | EWOCS Draft PWS | 22 | 2.9.3 | "For 30 SW and MDA transportation needs, the contractor shall use the Vandenberg AFB (VAFB) Transportation Management Office (TMO) to ship and receive freight to and from VAFB to the fullest extent possible." | This PWS is not assigned to the MDA CLIN. Please clarify. | MDA shipping/receiving execution is per the 30 SW SOP. Associated with CLIN X203 WR and MDA Reimbursable/Materials. | |
| 38 | EWOCS Draft PWS | 23 | 2.9.5 | "The contractor shall obtain an organizational code assigned through supply and order blank Vehicle Identification Link (VIL) keys through supply. Submit a letter to 30 LRS/LGRMF requesting VIL key(s) to be encoded. The contractor’s letter must be indorsed/signed by the Administrative Contracting Officer (ACO). (The ACO’s signature/endorsement is required to ensure that the contractor is authorized Government fuel. The letter must include type of fuel; tank/vehicle registration number; organizational code. (If fuel is to be off-loaded into a tank, indicate the tank size and request for a mobile servicing support; if it is for a vehicle, it must utilize the base government service station, not Army and Air Force Exchange Service (AAFES.))" | Are there a set of similar instructions for the 45th Space Wing and MDA? | MDA requirements included with 30 SW scope. Also applies to 45 SW. Paragraph adjusted for clarity. | |
| 39 | EWOCS Draft PWS | 23 | "The contractor shall use ILS-S as the primary source for material items. Purchasing from outside sources (Reimbursable Material CLIN) is authorized when ILS-S cannot fulfill requirements, support schedule or when lack of funding does not permit acquisition through ILS-S." | In Section B of the solicitation, the material CLINs states that "In accordance with the Federal Acquisition Regulation, Information Technology supplies and equipment shall be purchased through GSA unless a waiver is granted." Will the Government please clarify when we are to use which sources? | All purchases shall be made through the CAP/Reimbursable CLIN. The contractor shall utilize AFWAY/GSA whenever possible. | ||
| 40 | EWOCS Draft PWS | 24 | 2.9.8.5 | "Spares Identification: The contractor shall identify spares needed for existing, new, and modified equipment for MDA systems. The range and depth of spares will be based upon historical usage of the systems or like systems." | Are the spares referenced here to be purchased as a part of this contract? If so, which CLIN should contain these costs? | Pararaph adjusted to include all systems. Spares will be transferred during transition and managed thereafter. The costs should be billed on X103 & X203 Reimbursable/Material CLINs. | |
| 41 | EWOCS Draft PWS | 24 | 2.9.8.5 | "Spares Identification: The contractor shall identify spares needed for existing, new, and modified equipment for MDA systems. The range and depth of spares will be based upon historical usage of the systems or like systems." | Please clarify if this work is also necessary for the ER and WR? | Yes, see above. | |
| 42 | EWOCS Draft PWS | 24 | 2.9.8.5 | "Spares Identification: The contractor shall identify spares needed for existing, new, and modified equipment for MDA systems. The range and depth of spares will be based upon historical usage of the systems or like systems." | The labor associated with this PWS task is not included in the CLIN structure for MDA. Please clarify which CLIN should contain the labor associated with this work. | Reccurring standard logistics support for MDA should be charged to the 30SW Comm CLIN. Specifics one-time tasks related to specialized logistics will be ordered against the MDA CLIN as requested. | |
| 43 | EWOCS Draft PWS | 26 | 2.12.3 | "The Contractor will require entry authorization credentials on day one of the contract operational performance; Automated Entry Control Cards (AECC) for unescorted entry into controlled and restricted areas." | Is the contract award date before the actually contract start? If so, then meeting this requirement on Day one is possible. If not, then this requirement could not be met unless the Government commits to completing the processing of requests on Day One. | Yes, base and restricted area access will be worked during the transition period. | |
| 44 | EWOCS Draft PWS | 26 | 2.12.3 | There are two paragraphs that have this number on this page. | Please confirm that both of these paragraphs should be 2.12.3. | These paragraphs have been renumbered. | |
| 45 | EWOCS Draft PWS | 29 | 2.13.1 | "Maintain and execute a site-specific Local Restoration Plan (LRP) and Contingency Operations Plan (COP) for both 45 and 30 SW and Geographically Separated Units (GSUs)." | Are the current plans available as GFP as the requirement is to "Maintain and execute" not develop? Will the Government please provide them as part of the bidder's library? | Develop was added to the PWS paragraph. | |
| 46 | EWOCS Draft PWS | 32 | 2.15.1 | "The places of performance shall be: Patrick AFB, FL and CCAFS for 45 SW (ER) and Vandenberg AFB, CA for 30 SW (WR), and associated GSUs." | Will the contractor be required to have manning physically at the GSU’s, or can they be managed remotely/virtually | They can be managed remotely; however they may be dispatched as needed. | |
| 47 | EWOCS Draft PWS | 33 | 2.16.6 | "Adjust hours of operation based upon government operational priorities. Support Government scheduled activities outside of routine working hours due to mission requirements, launch windows, and hazards associated with range operations." | While this section and others provide scenarios to support outside of normal duty hours, will the EWOCS contractor be required to stand down from making changes to the Base Comm infrastructure due to Launch activities, (i.e.: Frame Light on the WR, or digging in the ground, etc...)? | Yes. | |
| 48 | EWOCS Draft PWS | 33 | 2.16.7 | "Outside the Principal Period of Maintenance (OPPM) is defined as all-time other than the Principal Period of Maintenance." | Will the Government please define what is the "Principal Period of Maintenance"? | Principal Period of Maintenance is the core wing duty hours. | |
| 49 | EWOCS Draft PWS | 38 | 3.5.1 | "Perform A&A RMF process at all locations, including Ascension AFB with input provided by the Ascension Island Mission Support (AIMS) Contractor." | How will the Government facilitate data transfer with the AIMS contractor (and others, indicated throughout PWS)? If the Government will not facilitate data transfer, how will contractors be held accountable for providing all required data to ensure successful RMF (and other) activities? | Associate Contract Agreements and CIPS work orders. | |
| 50 | EWOCS Draft PWS | 42 | 3.5.46 | Sections 3.5.46.1 - 3.5.46.33 | Within this section of cyber security many of the sub sections directly call out 45SW or 45SW systems. Do these sections not apply to the 30SW also? | PWS has been modified to reflect both wings. | |
| 51 | EWOCS Draft PWS | 44-45 | 3.5.46.24 thru 3.5.46.33 | 3.5.46.24 thru 3.5.46.33 | Many of the sections mention the 45 SW only, but they seem like they should apply to the 30 SW also. Please clarify if these are also applicable to the 30 SW? | PWS has been modified to reflect both wings. | |
| 52 | EWOCS Draft PWS | 49 | 3.7.29 | "Manage the Test Measurement & Diagnostic Equipment program IAW TO 00-33A-1001, METHODS AND PROCEDURES GENERAL CYBERSPACE SUPPORT ACTIVITIES MANAGEMENT PROCEDURES AND PRACTICE REQUIREMENTS, Chapter12." | Is this only for the EWOCS equipment or is this Base wide? | EWOCS equipment only. | |
| 53 | EWOCS Draft PWS | 52 | 3.7.38 | "Report, review, disseminate, direct and accomplishment/compliance of time change management (e.g. TCTO, TCNO, FCO, time change items, etc.)…" | Will there be a Technical Manual Contracts Requirement (TMCR) document delivered with the final RFP? If not, how will the contractor be put on contract for Technical Order requirements to accompany the PWS? |
Note: TCTOs are identified again in section 3.7.39.20.5.
| Are there other TOs required for delivery with this contract? | Items such as TCTO MTO are issued on a regular basis from the INOSC to the units. We are not providing TMCR in this RFP. Government is not requesting delivery of Tech Orders. | ||||||
| 54 | EWOCS Draft PWS | 53 | Multiple | ||||
| Examples in column E | Throughout the PWS, there are multiple documents identified. Ex. site set up status (3.7.38.7), data trend analysis (3.7.39), continuity book (3.7.39.12), etc. There is no defined format, delivery timeline, etc. | Is there an acceptable documentation format/examples/etc. for the identified deliverables (outside CDRLs), or are they contractor-defined? If contractor-defined, will there be minimum requirements and/or standards? Are there delivery deadlines, Gov't review timelines, delivery methods, etc? | There is no defined format examples, they are contractor-defined. Para 3.7.8.7 has been reserved. | ||||
| 55 | EWOCS Draft PWS | 53 | 3.7.39.12 | "Develop, document and maintain a continuity book of all procedures required to perform CFP duties. These should include but not limited to: Service Level Agreements (SLAs), Memorandums of Agreement (MOAs), Memorandums of Understanding (MOUs)." | Are there any existing SLAs, MOAs and MOUs? If so, would the Government please provide them to facilitate staffing understanding. | There are no SLAs. Available MOUs and MOAs will be posted to the bidders library. | |
| 56 | EWOCS Draft PWS | 53 | 3.7.39.7. | "Capture trouble ticket/job documentation error trends in the Communications Plan per Appendix D." | A Communications Plan is not listed in Appendix D. | Updated paragraph to state that it is needed as a Communications Plan IAW TO 00-33A-1001, METHODS AND PROCEDURES GENERAL CYBERSPACE SUPPORT ACTIVITIES MANAGEMENT PROCEDURES AND PRACTICE REQUIREMENTS. | |
| 57 | EWOCS Draft PWS | 54 | 3.7.39.17 | "Develop, document and maintain Communications Plan according to Appendix D." | A Communications Plan is not listed in Appendix D. | Updated paragraph to state that it is needed as a Communications Plan IAW TO 00-33A-1001, METHODS AND PROCEDURES GENERAL CYBERSPACE SUPPORT ACTIVITIES MANAGEMENT PROCEDURES AND PRACTICE REQUIREMENTS. | |
| 58 | EWOCS Draft PWS | 61 | 3.10.1.9 | "Ensure networks are operationally available 24 hours a day, 7 days a week with the following exceptions: Wing or higher HQ directed down time, pre-coordinated downtime for system-wide maintenance, or when contingencies prevent system availability, (i.e., system-wide power outages and natural disasters)." | If there are network outages upstream of the EWOCS boundary of responsibility will the EWOCS contractor still be held liable and take a performance hit? | The EWOCS contractor will not be held liable. | |
| 59 | EWOCS Draft PWS | 62 | 3.10.1.18 | ||||
| 3.10.1.22 | "Operate, maintain and configure point-to-point, VPN and bulk encryption for network and long-haul circuits." | Duplicate requirements, please remove. | The duplication has been removed. | ||||
| 60 | EWOCS Draft PWS | 65 | 3.10.4.18 | "Coordinate and test the LRP and COP quarterly and after hours without interfering with other operations to ensure that operational capability is restored and report results to the Help Desk." | Is this a real exercise with real hardware at a real alternate location or just a virtual exercise? This makes a difference from a bidding point of view. | This is a virtual exercise. | |
| 61 | EWOCS Draft PWS | 72 | 3.11.2.8 | "Provide planning and engineering support in developing the architecture to meet goals of Range of the Future (ROTF). Communications services for future operational systems related to ROTF shall be accomplished according to other sections of paragraph 3 of this PWS." | Can a workload factor summary sheet and/or more information be provided to understand the amount of "planning and engineering support" required? | This is requirement is not applicable on day 1 for the 45 SW and 30 SW. | |
| 62 | EWOCS Draft PWS | 73 | 3.12.1 | "Systems include, inside plant cable systems, circuits, distribution facilities/equipment, operational voice systems, and other MDA range interfaces such as telemetry transport systems, missile liftoff, status and alert, Closed Circuit Television (CCTV) and countdown clock/display." | Can the government provide a list of GFE tools and equipment for OM&S (i.e. Bit Error Rate Testers, Fiber Optics test equipment, etc.)? | All available GFE will be posted to FBO. | |
| 63 | EWOCS Draft PWS | 73 | 3.12.1 | Systems include, inside plant cable systems, circuits, distribution facilities/equipment, operational voice systems, and other MDA range interfaces such as telemetry transport systems, missile liftoff, status and alert, Closed Circuit Television (CCTV) and countdown clock/display. | Is the contractor required to perform OM&S of telemetry processing and display systems or just transport of raw telemetry from the Range demarcation to the LCC? | PWS para modified. Only for systems identified in Appendix C (Comm Systems and Services Matrix). | |
| 64 | EWOCS Draft PWS | 73 | 3.12.1 | Systems include, inside plant cable systems, circuits, distribution facilities/equipment, operational voice systems, and other MDA range interfaces such as telemetry transport systems, missile liftoff, status and alert, Closed Circuit Television (CCTV) and countdown clock/display. | Can the government provide a list of communications systems and major components? | PWS para modified. Systems are identified in Appendix C (Comm Systems and Services Matrix). | |
| 65 | EWOCS Draft PWS | 73 | 3.12.2 | "Contractor Work Breakdown Structure (CWBS). The contractor shall identify, document and use a CWBS to organize, define, and graphically display products to be produced as well as services to be provided. Make appropriate subdivisions as necessary to support internal management and data collection. Use CWBS as a basis for contract planning, budgeting, cost and schedules status. Updates or revisions to the CWBS shall be made as required with prior Government Program Manager (PM) approval. (CDRL M002)" | Is this CWBS a unique CWBS for MDA only or is it part of the EWOCS CWBS with MDA work isolated? | Para deleted and is now reserved. MDA CWBS included in overarching CWBS for the contract. | |
| 66 | EWOCS Draft PWS | 73 | 3.12.2 | "Contractor Work Breakdown Structure (CWBS). … (CDRL M002)" | CDRL M002 not included in CDRL list. | Para deleted and is now reserved. MDA CWBS CDRL has been deleted. | |
| 67 | EWOCS Draft PWS | 73 | 3.12.2 | "Contractor Work Breakdown Structure (CWBS). The contractor shall identify, document and use a CWBS to organize, define, and graphically display products to be produced as well as services to be provided. Make appropriate subdivisions as necessary to support internal management and data collection. Use CWBS as a basis for contract planning, budgeting, cost and schedules status. Updates or revisions to the CWBS shall be made as required with prior Government Program Manager (PM) approval." | The MDA incumbent (InDyne) currently utilizes a proprietary program management tool (PIMS360) they market as a product for purchase. We have attempted to contact the incumbent to request licensing pricing but the incumbent has been non-responsive. Without a license we are unable to utilize the tool to transition data to the new contract. Please explain how the incumbent will transfer data from PIMS to the successful contractor. At a minimum, the following data needs to be transferred: |
- Configuration Management Documents
- Circuit Records
- As-Built Drawings
- Data Products
- Scheduled/Unscheduled Maintenance Records
- MoRRs
| - IA documentation | Para deleted and is now reserved. PIMS is not a mandated tool. An Integrated Data Management System is required. See requirements of system in PWS. There is no preferred tool as long as it meets the requirements and is authorized to run on the AF network. | ||||||
| 68 | EWOCS Draft PWS | 73 | 3.12.3 | "Meetings and Reviews. The contractor shall participate in meetings and reviews as requested by the Government. Such meetings may include requirements definition and Technical Interchange Meetings (TIMs) through task/project completion. Conduct Progress Report Meetings to provide the Government status of projects. The Contractor shall produce meeting minutes and list of attendees within 3 days. (CDRL A002)" | Are these meetings to be conducted as part of the EWOCS meetings? | Yes, these are EWOCS related meetings. Para has been adjusted. Refer to adjusted CDRL A002. | |
| 69 | EWOCS Draft PWS | 73 | 3.12.3 | "Meetings and Reviews. The contractor shall participate in meetings and reviews as requested by the Government. Such meetings may include requirements definition and Technical Interchange Meetings (TIMs) through task/project completion. Conduct Progress Report Meetings to provide the Government status of projects. The Contractor shall produce meeting minutes and list of attendees within 3 day. (CDRL A002)" | CDRL A002 in the CDRL list is identified as "Contractor's Progress, Status and Management Report". There is no CDRL for MDA Meeting Minutes. | Meetings minutes should be part of General Program Management (CDRL A002). | |
| 70 | EWOCS Draft PWS | 74 | 3.12.5.2 | "The contractor shall implement all approved MoRR documents to meet completion requirements as indicated in Table 3.3, MoRR Priorities." | Can the government provide workload factors for annual MoRR requirements by priority? | 3.12.5. modified from MoRR to MDA Work Orders. MoRR Workload factors are spread across overall MDA workload factors. | |
| 71 | EWOCS Draft PWS | 74 | 3.12.5.2 | "Priority Levels A-1 will include emergency requirements with overtime authorized. Priority Levels A-2 will include emergency requirements with no overtime authorized. Priority Levels A-2 will include emergency requirements with no overtime authorized. Priority Levels A-3 will include emergency requirements that may take extra time due to material shortages, customer incurred delays, etc. Government PM or designated alternate will approve all priority Level A’s and Level B’s." | A CLIN for MDA overtime does not exist. Please clarify. | A CLIN for MDA Overtime is not required because it is CPFF. | |
| 72 | EWOCS Draft PWS | 74 | 3.12.6.1 | "Configuration Management and Control Plan: The contractor shall develop, deliver and maintain a Configuration Management (CM) Plan IAW DI-CMAN-80858 using the GMD Configuration Management Plan (GCMP) as a guide. The contractor’s configuration management plan shall address each section of the GCMP as applicable. The contractor shall deliver engineering changes as required IAW DI-SESS-80639, DI-SESS-80642 and DI-SESS-80643. The contractor shall only incorporate changes to the affected hardware after Government approval of the ECP. The contractor shall establish and maintain the Product Baseline, for all data and systems under its development, installation, and maintenance responsibility and report that as an as-built baseline IAW CDRL M006, As Built Documentation List. Modifications or MWOs to the baseline shall be approved and implemented only after an ECP is submitted and approved by the Government IAW the GCMP. (CDRL M005 and M006)" | Will a Bidders Library be posted to include the following documents referenced in this PWS paragraph: |
- GMD Configuration Management Plan
- DI-CMAN-80858
- DI-SESS-80639
- DI-SESS-80642
| - DI-SESS-80643 | No. Requirement was modified. Pertinent data will be posted to the bidder's library. | ||||||
| 73 | EWOCS Draft PWS | 75 | 3.12.6.1 | Configuration Management and Control Plan: ... (CDRL M005 and M006)" | CDRL M005 and M006 not included in CDRL list. | Revised. No longer required. | |
| 74 | EWOCS Draft PWS | 75 | 3.12.6.2 | "Configuration Baseline: … (CDRL M007)" | CDRL M007 not included in CDRL list. | Revised. No longer required. | |
| 75 | EWOCS Draft PWS | 75 | 3.12.6.4 | "Data Management: The contractor shall develop, implement, and maintain a centralized management information system that provides information on demand to include but not limited to, work status, CDRLs, records, and drawings. All data will be turned over in whole to the Government in utilized format upon contract end date. Develop and follow approved Data Management Plan for contract data tracking and delivery. Designate a focal point to integrate total data management efforts. Manage documentation and delivery of data as listed and scheduled on CDRLs, and changes, additions, and deletions of data items. Identify additional data items and recommend revisions and deletions of items listed on the CDRL. Unless otherwise stated, all CDRLs shall be delivered in electronic format." | The MDA incumbent (InDyne) currently utilizes a proprietary program management tool (PIMS360) they market as a product for purchase. We have attempted to contact the incumbent to request licensing pricing but the incumbent has been non-responsive. Without a license we are unable to utilize the tool to transition data to the new contract. Please explain how the incumbent will transfer data from PIMS to the successful contractor. At a minimum, the following data needs to be transferred: |
- Configuration Management Documents
- Circuit Records
- As-Built Drawings
- Data Products
- Scheduled/Unscheduled Maintenance Records
- MoRRs
| - IA documentation | PIMS is not a mandated tool. An Integrated Data Management System is required. See requirements of system in PWS. There is no preferred tool as long as it meets the requirements and is authorized to run on the AF network. | ||||||
| 76 | EWOCS Draft PWS | 75 | 3.12.6.4 | Data Management: Develop and follow approved Data Management Plan for contract data tracking and delivery. Designate a focal point to integrate total data management efforts. Manage documentation and delivery of data as listed and scheduled on CDRLs, and changes, additions, and deletions of data items. Identify additional data items and recommend revisions and deletions of items listed on the CDRL. Unless otherwise stated, all CDRLs shall be delivered in electronic format. | No CDRL has been identified for development of a Data Management Plan. | No separate Data Management Plan required for MDA. | |
| 77 | EWOCS Draft PWS | 75 | 3.12.6.5 | "The contractor shall provide an estimated recurring cost to deliver each data item. This recurring cost will be used to delete data items that are no longer required and as a basis from which to negotiate additional data requirements with the same or very similar DIDs. The Government may, pursuant to the "Changes" clause, delete data requirements from Exhibit 7. In the event data is deleted for an entire contract year(s), the amounts reflected in Block 18, DD Form 1423-1 shall be the amounts unilaterally deducted from the contract estimated costs for the years involved. In the event data is deleted for less than an entire contract year, the amounts deducted shall be unilaterally pro-rated on the basis of calendar months." | This paragraph appears to be written for a CPFF contract yet the MDA CLIN is FFP. Please clarify. Also, the paragraph references Exhibit 7, but no Exhibit 7 exists. | RFP has been changed to reflect CPFF. No exhibit 7 exists. | |
| 78 | EWOCS Draft PWS | 76 | 3.12.7 | "The contractor shall provide hardware, software and interface preventive/corrective maintenance, launch operations support, GMD Launch Control Center (LCC) configuration management and cybersecurity services of launch communication systems within the MDA program" | Within the MDA section 3.12 there are additional sections provided on all the tasks motioned in 3.12.7 with the exception of launch operations support. Will additional information be provided to detail what tasks will be required to meet launch operations support and if this is just for launches or includes any tests? | Support is required for all MDA Test Events. Launch OPS support for Flight Test included in UDS doc. | |
| 79 | EWOCS Draft PWS | 76 | 3.12.7 | "The contractor will also provide mission security support at all MDA facilities on VAFB." | Can the Government provide more specifics on the type of security support required? | Requires security escorting access control. Paragraph 3.12.7 modified. | |
| 80 | EWOCS Draft PWS | 76 | 3.12.7.1 | "Hardware, Software and Interface Maintenance: The contractor shall provide preventive/corrective scheduled/unscheduled maintenance of the systems and interfaces listed in Appendix G, Systems Listing." | Appendix G is not included in the PWS. | Use Appendix C, Comm Services and Systems Matrix | |
| 81 | EWOCS Draft PWS | 78 | 3.12.10.2 | "The contractor shall support cyber security Risk Management Framework (RMF), artifact development, maintenance, patching, testing, and updates/upgrades IAW DoDI 8500.01 Cybersecurity, DoDI 8510.01 Risk Management Framework for DoD Information Systems, National Institute of Standards and Technology (NIST) SP 800-53 Security Privacy Controls for Federal Information Systems and Organizations, and Committee on National Security Systems Instructions (CNSSI) 1253 Security Categorization and Control for National Security Systems, or the most current versions and support assessment and authorization activities for systems listed in Appendix G, MDA Systems Listing." | Can the government provide workload factors regarding the annual number of RMF packages developed / maintained by the contractor? | Use updated Systems and Services Matrix. | |
| 82 | EWOCS Draft PWS | 78 | 3.12.10.3 | "The contractor shall develop a Cybersecurity Implementation Plan (CIP) (CDRL M008)." | CDRL M008 is not included in the CDRL list. | Updated to M002 | |
| 83 | EWOCS Draft PWS | 79 | 3.12.10.4 | "The contractor shall provide certified technical support IAW DODI 8570 for the assessment and authorization of all MDA Automation Information Systems (AIS) and Information Technology Systems (ITS) under the contractor’s control." | This requirement implies the contractor will be responsible for AIS and IT systems over and above the communications systems identified in paragraph 3.14.1. Please provide a list of all systems to be placed under the contractor’s control. | See MDA systems listed in Appendix C Services and Systems Matrix. Refer to current PWS. | |
| 84 | EWOCS Draft PWS | 79 | 3.12.10.4.1.1.1 | "Perform periodic system scans and update A&A documentation." | Will the government provide required scanning tools as GFE to meet this requirement? | Yes. | |
| 85 | EWOCS Draft PWS | 81 | 3.12.10.5 | "The contractor shall appoint ISSOs, SAs, and NAs as appropriate, for systems operated by the contractor per applicable Government directives (See Table 3-1 for applicable systems and for required skill sets)." | No Table 3-1 is provided. | Updated PWS statement. | |
| 86 | EWOCS Draft PWS | 81 | 3.12.10.5 | "The contractor shall appoint ISSOs, SAs, and NAs as appropriate, for systems operated by the contractor per applicable Government directives (See Table 3-1 for applicable systems and for required skill sets). Personnel appointed as ISSOs, SAs and/or NAs shall be trained IAW DoDI 8570 as Information Assurance Technical (IAT) II personnel. Contractor will ensure personnel assigned these duties possess required security clearances IAW appropriate DoD and MDA guidance. SAs and NAs will require minimum Secret security clearance; ISSOs shall obtain and maintain Top Secret clearance if privileged access is required." | Paragraph states that the contractor will provide System Administrators and Network Administrators. Is the contractor responsible for information assurance of systems other than the systems identified in paragraph 3.12.1? | See Appendix C, Comm Services and Systems Matrix | |
| 87 | EWOCS Draft PWS | 81 | 3.12.10.6 | "The contractor shall develop, maintain, and provide Incident Response and Reporting Plan annually or as required. The Incident Response and Reporting Plan shall be tested and exercised bi-annually. The Contractor shall identify and report cybersecurity vulnerabilities or deficiencies to Operational Site Management and the cognizant government ISSO during the course of operations IAW the current Incident Response and Reporting Plan and documented within the CIP. (CDRL M009)" | CDRL M009 not included in CDRL list. | Updated PWS to M003. | |
| 88 | EWOCS Draft PWS | 81 | 3.12.10.7 | "(CDRL ???)" | Please provide the CDRL number for this reference. | Updated PWS to M004. | |
| 89 | EWOCS Draft PWS | 81 | 3.12.10.7 | "The Contractor shall develop, and maintain a Disaster Recovery Continuity of Operations Plan (DR/COOP). The Contractor shall execute the DR/COOP if warranted. The contractor shall train assigned personnel in DR/COOP responsibilities. The Contractor shall test and exercise DR COOP bi-annually or as required by RMF. (CDRL ???)" | Is this a real exercise with real hardware at a real alternate location or just a virtual exercise? This makes a difference from a bidding point of view. |
| Is there an existing plan in place? | Virtual tabletop exercise is acceptable. | ||||||
| 90 | EWOCS Draft PWS | 81 | 3.12.10.7 | "The Contractor shall develop, and maintain a Disaster Recovery Continuity of Operations Plan (DR/COOP)." | Does the Government intend to include a CDRL for the Disaster Recovery Continuity of Operations Plan (DR/COOP)? | Yes reference M004 | |
| 91 | EWOCS Draft PWS | 84 | Appendix B | Is the Government going to provide the complete QASP with the Final RFP or before? | Provided during transition. | ||
| 92 | EWOCS Draft PWS | NA | NA | Multiple references to existing tools/technologies. | Is the Government open to using new tools/technology, or sticking with only those systems referenced in the PWS? | After award the Government is open to using new tools/technology. | |
| 93 | EWOCS Draft PWS | Multiple | Multiple | The terms "45 SW," "ER," "30 SW," etc. are used throughout the PWS. However, many tenant organizations, e.g., AFTAC, DEOMI, 920 RQW, NRO, etc. are not specifically mentioned. | In addition to 30 SW and 45 SW units, 30 SW/45 SW contracted support, and launch mission partners; what other tenant units will have their requirements sourced through EWOCS? | The Government's customers vary from year to year. | |
| 94 | Draft PWS Appendix C EWOCS Systems and Services 28 Jun 19 | 1,2 | This document provides workload factors for 45 SW EPIC projects, will there be workload support numbers for the 30 SW SURF projects? | All requirements will be provided in updated documentation (Appendix C, Comm Systems and Services Matrix and PWS 3.11.2) in the Final RFP. | |||
| 95 | Draft PWS Appendix C EWOCS Systems and Services 28 Jun 19 | N/A | All | The EWOCS MDA Workload Factors table includes hours for the following services not identified in PWS 3.12: |
- Help Desk Support
- Network Control Center Support
- Enterprise Information Technology
- IT Web/Applications Development
- Logistics Management
- Security Systems
| Are these services required as part of the separate MDA Task Order? If so, will the PWS be amended to define these services? | No, these services are provided under the baseline 30 SW CLIN, X201. | ||||||
| 96 | 03_EWOCS_Draft_Section_L | 10 | 3.1 | "Only submit those projects for which the Offeror, Major Subcontractors (15% of total contract value), Primary Teaming Partners, or Joint Venture Partners performed and are proposed to perform in this RFP. " | Please define "Primary Teaming Partners"? | Wording has been changed to state teaming partner instead. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .