Q As_19_Dec_2013.pdf

Range Operation Support

FA2521-13-R-0005

QUESTION AND ANSWER

1) RFP Section _______________Paragraph __________________ PWS Paragraph 3.1.1.1_ Other (Specify) ___________

Question:

Is there presently a valid Waiver/Deviation to operate below DoDI 6055.06 for Installation Fire Protection staffing? If so, will the Government please provide offerors with a copy of this document?

ANSWER: No, there is not an approved waiver.

2) RFP Section _______________Paragraph __________________ PWS Paragraph 3.1.1.1____ Other (Specify) ___________

Question:

Is an Aircraft Live Fire Training simulator available on Antigua or Ascension or are fire fighters sent off island to meet the requirement of aircraft live fire training not less than two times a year?

ANSWER: No. All live fire simulator training is performed by the Patrick AFB Fire Dept at Patrick AFB.

3) RFP Section _______________Paragraph __________________ PWS Paragraph 3.1.1.1.8____ Other (Specify) ___________

Question:

How many years are the Mutual Aid Agreements for emergency services valid? Will they have to be renewed at any point during this contract?

ANSWER: The length of each agreement is indicated on that agreement or in treaty stipulations. All current documents have been posted in the Bidders Library.

4) RFP Section _______________Paragraph __________________ PWS Paragraph 5.1.13____ Other (Specify) ___________

Question:

PWS Section 5.1.13 requires that the contractor obtain IA accreditations. Much of the Nortel telephone switching and voice mail system is no longer OEM supported since Nortel went bankrupt and pieces were sold off to Avaya and Genband. As a result, some of that equipment will never meet modern STIGs. Will the Air Force provide IA type accreditations and DAA approval for legacy equipment?

ANSWER: Systems are currently accredited and the Patrick AFB IA Manager will work with the contractor team to ensure continued accreditation.

5) RFP Section _______________Paragraph __________________ PWS Paragraph 5.1.8.6____ Other (Specify) ___________

Question:

PWS Section 5.1.8.6 requires "installation/removal" of some possibly large scale systems such as switching systems, frames, battery, rectifiers, etc. Will the Government please clarify PWS Section 5.1.8.6 requires only replacement of defective items, such as line/trunk cards required for operation and maintenance of the system, and not switching system replacement?

ANSWER: The scope of this paragraph is to ensure systems remain operational.

6) RFP Section _______________Paragraph __________________ PWS Paragraph 5.1.8.6____ Other (Specify) ___________

Question:

The PWS references VoIP service at Antigua and Ascension, but no telephone components are identified on the network diagram provided in the Bidder’s Library. Is there a resident Cisco Call Manager server at Antigua and Ascension or is VoIP service extended by the WAN from a remote server cluster?

ANSWER: There is currently no VoIP capability or hardware installations at any downrange site but the contractor will be expected to have expertise to support VoIP.

7) RFP Section _______________Paragraph __________________ PWS Paragraph _________ Other (Specify) ROS Communications Site Visit information posted to FBO 4/29/13, File Name: ROS_Comm_Pkg _042313.pdf___________

Question:

There is a large Nortel telephone switching system and multiple Nortel channel banks at CCAFS; however, we cannot locate information on the hardware/software version or the configuration of the card complement (i.e. how many analog/digital/ISDN lines and trunks). Will the Government please provide this information or direct offerors where to find it if it has already been made available?

ANSWER: Information will be provided on the Bidders Library.

8) RFP Section _______________Paragraph __________________ PWS Paragraph _________ Other (Specify) ROS Communications Site Visit information posted to FBO 4/29/13, File Name: ROS_Comm_Pkg _042313.pdf

Question:

The drawing in the referenced file has a legacy Nortel Call Pilot voice mail system at CCAFS. Does this provide voice mail for all locations?

ANSWER: Yes.

9) RFP Section _______________Paragraph __________________ PWS Paragraph __5.1 Other (Specify) ___________

Question:

Does the cabling infrastructure support include maintenance of the Inside Cable Plant (ISP) and Outside Cable Plant (OSP) or only the drawing maintenance as detailed in Paragraph 5.1.6? Are as-built communications drawings available to determine the split (%) between copper/fiber and the existing cable pathway systems for the communications infrastructure if maintenance is required? Will the Government please provide this information or direct offerors where to find it if it has already been made available?

ANSWER: 1 - No. 2 - No 3 - Available as-builts are provided on Bidders Library.

10) RFP Section _______________Paragraph __________________ PWS Paragraph __5.1.1 Other (Specify) ___________

Question:

Do the demarcation points between Mission Support Communications and Mission Communications currently exist or are they being established as part of this contract with the installation of demarcation patch panels/terminal blocks? Can offerors expect all existing communication cabling to be labeled in accordance with an approved standard and documented on as-built drawings? Will the Government please provide this information or direct offerors where to find it if it has already been made available?

ANSWER: Question 1 - The demarcs currently exist but may require replacement if deemed necessary. Question 2 - Standard marking and coding are used.

Question 3 - Bidders library has all available information on communication connectivity and devices.

11) RFP Section _______________Paragraph __________________ PWS Paragraph __5.1.1.2

Other (Specify) ___________

Question:

Will there be a formal agreement (MOA/MOU) between the ROS Contractor and the OM&S contractor detailing communication support responsibilities between the contractors? Will the Government please provide this information or direct offerors where to find it if it has already been made available?

ANSWER: Question 1 - An associate Contractor Agreement can be established.

Question 2 - This is not currently available.

12) RFP Section _______________Paragraph __________________ PWS Paragraph __5.1.3.1.5 Other (Specify) ___________

Question:

Does this mobile phone support requirement include the maintenance and support of the user handheld units? If yes, is information available to determine the number of units? Will the Government please provide this information or direct offerors where to find it if it has already been made available?

ANSWER: 30 SW only. No. The mobile phones are the responsibility of the user who must register them with the ROS contract.

13) RFP Section _______________Paragraph __________________ PWS Paragraph _5.1.4 Other (Specify) ___________

Question:

Are as-built VESS drawings available for offerors to determine the size and complexity of this security system? If so, will the Government please provide these items or direct offerors where to find them?

ANSWER: No. These drawings are operationally sensitive and will be released to the ROS contractor once awarded.

14) RFP Section _______________Paragraph __________________ PWS Paragraph _5.1.5 Other (Specify) ___________ Question:

We assume Move-Add-Change (MAC) services are included in support under PWS Section 5.1.5. Is this a correct assumption? If so, is there any historical date on the expected number of MACs per month per site?

ANSWER: Question 1 - Yes. Question 2 - No.

15) RFP Section _______________Paragraph __________________ PWS Paragraph _5.1.5 Other (Specify) ___________

Question:

Are as-built network drawings available for offerors to review the existing network to determine the size and complexity? If so, will the Government please provide these items or direct offerors where to find them?

ANSWER: They are provided on the Bidders Library except for those areas that are operationally sensitive.

16) RFP Section _______________Paragraph __________________ PWS Paragraph _________ Other (Specify) ROS Communications Site Visit information posted to FBO 4/29/13, File Name: ROS_Comm_Pkg _042313.pdf

Question:

Will the Government please provide information regarding the hardware/software versions of primary and secondary crash conference systems?

ANSWER: Yes. The company that made the system is Forum Communications at http://www.forum-com.com/pdfs/AlertBrochure20084pp.pdf. All material will be provided on the Bidders Library at next update.

17) RFP Section _______________Paragraph __________________ PWS Paragraph _5.1.8 Other (Specify) ___________

Question:

How is telephone service extended to JDMTA and Malabar?

ANSWER: Over standard POTS

18) RFP Section PWS Paragraph N/A PWS Paragraph 1.1 Other (Specify) N/A

Question: Third paragraph states, "...non-mission Mission Support Communications for the ER and WR...". Please clarify what is meant by "non-mission Mission Support Communications".

ANSWER: See paragraph 5.1.1.1 of the PWS

19) RFP Section PWS Paragraph N/A PWS Paragraph 1.2.1 Other (Specify) N/A

Question: Section states, "The AAS Mission Support Communications role is to provide telemetry, communications, and timing and sequencing". Please clarify if this was intending to say that the AAS role is to provide these services in support to ER launch missions. Otherwise, please clarify what telemetry, timing and sequencing responsibilities fall to the ROS contractor.

ANSWER: The word “Support” has been deleted from this paragraph. The ROS contractor will provide Mission Support Communications as defined by the

PWS.

20) RFP Section PWS Paragraph N/A PWS Paragraph 1.2.1.4

Question: Section states that the AAS contractor is responsible for "emergency response, emergency medical response, and fire protection services for facilities, aircraft, and personnel. Since the airport at AAS is commercial/civilian, please provide clarification as to the role the ROS contractor provides either as sole provider or in an assisting role to the civilian airport emergency services.

ANSWER: The contractor provides base support in these areas and supports local authorities under treaty or MOU.

21) RFP Section PWS Paragraph N/A PWS Paragraph 1.2.2 Other (Specify) N/A Question: Section states, "The AAAF Mission Support Communications role is to provide radar tracking, space surveillance tracking, telemetry, timing and sequencing, and communications". Please clarify if this is the overall AAAF role or if these functions fall upon the ROS contractor. If so, please provide requirements in PWS relating to all these requirements.

ANSWER: The word “Support” has been deleted from the PWS.

22) RFP Section PWS Paragraph N/A PWS Paragraph 1.3

Question: Paragraph appears to be incorrectly bolded. This appears to be referencing the final paragraph under 1.2.3 as well as the start of "1.3 Mission Support Communications"

ANSWER: Paragraph is correct as written.

23) RFP Section PWS Paragraph N/A PWS Paragraph 1.3

Question: Section references, "…the ROS contractor will perform all Mission Support Communications for AAS and AAAF". Please clarify what is intended by "all" Mission Support Communications and what the demarcation of responsibility between the ROS contractor and the LISC OM&S contractor.

ANSWER: Demarcation defined in Section 5. Mission Support Comm includes admin comm. Support.

24) RFP Section PWS Paragraph N/A PWS Paragraph 1.3.1

Question: Sections states "…at all three locations…", yet the preceding sentence lists six locations. Please clarify what the three locations are referring to.

ANSWER: PWS corrected.

25) RFP Section PWS Paragraph N/A

Question: In reference to ER responsibilities, sections States, "…five areas of responsibility…", yet the sentences that follow list seven areas:

1) AFNETOPS Inegration -- Software Configuration -- Anomoly Tracking -- System Restoration -- Help Desk Inquiry Response (touch maintenance)

2) Operate and Maintain GIMS and GIS Database

3) Operate and Maintain Telephone Voice and Aural Warning Systems

4) COMSEC Management (up to Secret level)

5) Information Assurance & Physical IA Management

6) SIPRNet Services (AAAF and AAS only)

7) ATCALS Maintenance (AAAF only)

ANSWER: PWS corrected.

26) RFP Section PWS Paragraph N/A

PWS Paragraph 1.3.2

Question: In reference to WR responsibilities, the section States, "…three primary areas of responsibility…", yet the sentences that follow list four areas:

1) AFNETOPS Integration

2) GIS Database O&M

3) Information Assurance & Physical IA Management

4) Switchboard Operations and Maintenance.

Additionally, this does not capture the requirements listed in PWS section 5 outlining specific NIPR/SIPRnet server, desktop, and sofware support. Please clarify.

ANSWER: PWS corrected.

27) RFP Section PWS Paragraph N/A

Question: Please provide update on the status of VAFB being integrated into the AFNETOPs Service Support Model to include service desk calls, on-site support, and combined use of the consolidated service desk ticketing system.

ANSWER: Help Desk functions are described in paragraph 5.1.3 of the PWS.

Status will not be provided.

28) RFP Section PWS Paragraph N/A PWS Paragraph 1.3.2

Question: Please provide update on the status of PAFB, CCAFS, and all downrange (FL and off-shore) sites being integrated into the AFNETOPs Service Support Model to include service desk calls, on-site support, and combined use of the consolidated service desk ticketing system.

ANSWER: Help Desk functions are described in paragraph 5.1.3 of the PWS.

Status will not be provided.

29) RFP Section PWS Paragraph N/A PWS Paragraph 2.1.2

Question: Please clarify what is meant by "…positive management of employees…". Is the intent that the contractor provide "positive control" of employees, or to provide a "positive working environment" for employees?

ANSWER: Positive control of employees.

30) RFP Section PWS Paragraph N/A PWS Paragraph 2.1.3.1.1

Question: Please clarify what is meant by "level 1 of the PWS". Please provide an example of the PWS section/paragraph.

ANSWER: Level 1 of PWS is major paragraph level i.e 2.0 or paragraph 2.

31) RFP Section PWS Paragraph N/A PWS Paragraph 2.1.4.1 Other (Specify) N/A

Question: Sentence appears to be missing the work "and" between "developed" and "government".

ANSWER: PWS corrected.

32) RFP Section PWS Paragraph N/A PWS Paragraph 2.1.4.3 Other (Specify) N/A

Question: Section implies that the contractor developed and provided IDMS will require implementation of "roles-based security profiles that allow full control, restricted access, and limited access for personnel authorized access at the appropriate level based on need."

- Is it the Government's intent for the IDMS to be hosted inside the base firewalls?

- If so, will the Government sponsor the accreditation of the system?

- Will the DAA for system accreditation be at the 45SW or 30SW? or Both?

- Will the system require or allow external (outside or through the firewall) access since some of the data requested ?

ANSWER: 1. Yes. 2. 45SCS is the IA manager for 45 SW. 3. Both. 4. Yes.

33) RFP Section PWS Paragraph N/A PWS Paragraph 2.1.4.5 Other (Specify) N/A

Question: Please clarify "native file formats". What format(s) does/do the Government require the data in?

ANSWER: Native file format is the original format generated by an approved application.

34) RFP Section PWS Paragraph N/A PWS Paragraph 2.1.4.5.1.p Other (Specify) N/A

Question: Please clarify "COMMS-GIMS" versus other references to GIMS in the PWS.

Is there a separate GIMS system supporting 45 SW Communications and the 45 SW Civil Engineering functions? Please clarify.

ANSWER: GIMS has several layers. Comm GIMS is the layer providing comm.

Network layout.

35) RFP Section PWS Paragraph N/A PWS Paragraph 2.1.4.5.2.a Other (Specify) N/A

Question: Please clarify "previously developed data".

- What is this referring to?

- What format is this data provided in?

ANSWER: Legacy data. Ensure that the delivered data is the latest revision of the data application utilized. Format is dependent on the application but typically flat file unless otherwise indicated.

36) RFP Section PWS Paragraph N/A PWS Paragraph 2.3.1.3

Question: Will the Government be providing Government LAN access to contractor employees at PAFB, CCAFS, Malabar, and JDMTA?

ANSWER: At all locations required for performance of requirements.

37) RFP Section PWS Paragraph N/A PWS Paragraph 2.4.4

Question: Please clarify "range tours". Is the intent that the contractor will provide "on-site" tours? What is the historical frequency of such tours and how long do they typically last?

ANSWER: Tours of the range assets. Workload factors are provided in Workload Factors Table on Bidders Library.

38) RFP Section PWS Paragraph N/A PWS Paragraph 2.4.6.4

Question: Please clarify "Western Range Network Segment Center (WRNSC)". This paragraph implies that the contract will provide an NCC 24/7 at the Wester Range and will respond to all WRNSC emergency notifications. What is this organization and what is the role of the WRNSC as it applies to contractor provided services at the WR?

ANSWER: This is touch maintenance only and the 30SW manager is 30 SCS.

39) RFP Section PWS Paragraph N/A PWS Paragraph 3.1

Question: Paragraph states, "(ER Only unless otherwise noted)" for BOS services.

This implies that unless specifically noted in section 3.1 subparagraphs, that all noted BOS services will be provided at PAFB, CCAFS, Malabar, JDMTA, AAS, and AAAF.

Please clarify specifically what services are to be provided at which locations, otherwise the contractor is expected to assume that all non-noted requirements will apply to ALL ER locations. For example, paragraphs 3.1.1.1 and 3.1.1.2 state these apply to AAS and AAAF, but paragraph 3.1.1.3 does not clarify and it can be implied that these services apply to all Eastern Range locations.

ANSWER: This applies only to AAS and AAAF as applicable, PWS has been updated.

40) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.3

Question: This section states that this task supports AAS and AAAF unless otherwise noted, but fails to include the Vandenburg ESS (which is included in section 5.1.4. Is it the Government's intention that the ESS at AAS and AAAF be under the control of the BOS/CE function, whereas the Vandenburg ESS be under the control of the Communications function? Please clarify how these functions are currently being provided and what the Government's desire is for future O&M actions.

ANSWER: This is in a different section of the PWS – Section 5.1.4

41) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.3.3 Other (Specify) N/A

Question: What are the current ESS systems in place at AAS and AAAF? Please provide additional workload data and system specifications to allow appropriate operation and maintenance staffing/pricing estimates.

ANSWER: Vindicator systems as noted in comm. diagrams on Bidders Library.

42) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.3.5

Question: Are ESS replacement parts, spares, equipment considered GFE or contractor provided?

ANSWER: GFP

43) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.7.6

Question: Paragraph 3.1.7 states that "this task applies to all areas where ROS operates" which would include all locations at WR and ER.

- Is the GIS shared between the 30SW and 45SW or are these 2 separate systems?

- Is it the Government's intent for these systems to be integrated? or to remain separate between WR and ER?

- Is GIS access at remote downrange locations provided via network? or is there a GIS install at AAS and AAAF?

ANSWER: 1. No (separate installs) 2. No. 3. Network for server but local for clients. The PWS has been update to reflect that the task applies to all areas with the ROS AOR.

44) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.7.6.1

Question: Please clarify if the GIS system is Government provided, or if the contractor is expected to implement an enterprise GIS.

- Is the GIS Government provided?

- What is the role of the ROS contractor for this system?

ANSWER: 1. Yes 2. Maintainer and provide system drawing updates.

45) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.7.6.6

Question: What versions of AutoCAD and ArcSDE are required to be compatible with the GIS? Is this software considered GFE? How many licenses are provided to the contractor?

ANSWER: Considered GFP and provided on bidders library in Software Dictionary publication.

46) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9

Question: Please clarify where Maximo access is required across the ROS contract since the paragraph is preceded that this task supports both AAS and AAF.

ANSWER: Provided for in bidders library in Software Dictionary publication.

47) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9.5.6.1

Question: What version of Maximo is currently in place and are there any plans for system upgrade prior to contractor start?

ANSWER: Provided for in bidders library in Software Dictionary publication.

48) RFP Section PWS Paragraph N/A

Question: What Maximo modules are currently in use? To ensure data integrity from current contractor to new contractor, please clarify which Maximo modules are in use and are required.

ANSWER: Provided for in bidders library in Software Dictionary publication.

49) RFP Section PWS Paragraph N/A

Question: Are Maximo application servers GFE or contractor provided?

ANSWER: GFP. Provided in bidders library in Software Dictionary publication.

50) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9.5.6.3

Question: Paragraph states Maximo Software Module access and connectivity is via the 45 SW LAN, yet paragraph 3.1.9 states "this task supports both AAS and AAAF unless otherwise noted". Please clarify the expectation for Maximo access, where it is to be used, and who will require access.

ANSWER: AAS and AAF are on the 45 SW LAN. All users AAS and AAAF with a mission need will require access.

51) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9.5.6.4

Question: Task states that six Maximo Software Module licenses are required. Please clarify and provide details on which Maximo software modules are required and the quanitity of each module required. What is the total number of licenses required in addition to the six noted?

ANSWER: GFP. Provided in bidders library in Software Dictionary publication.

52) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9.8.5.1

Question: What systems are designated "mission essential systems"?

ANSWER: Systems that are required to support a space launch.

53) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9.15.2

Question: What facilities are designated "critical facility"?

ANSWER: Facilities that are required to support a space launch.

54) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9.17.4

Question: What facilities are designated "critical facility"?

ANSWER: Facilities that are required to support a space launch.

55) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9.17.10

Question: Please clarify what locations airfield lighting and navigational aid support is required. Is this support required at both AAS and AAAF as noted in paragraph 3.1.9?

ANSWER: AAAF only as noted in 3.1.9.17.10.

56) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9.18.4

Question: Do Florida Department of Transportation (DOT) regulations apply to AAS and AAAF?

ANSWER: Not specifically, however, the PWS requires the regulation be followed.

57) RFP Section PWS Paragraph N/A PWS Paragraph 3.1.9.18.8 Other (Specify) N/A

Question: Please clarifying "outlying sites" at AAAF for road maintenance.

ANSWER: Includes Cross Hill, radar 12.15 road.

58) RFP Section PWS Paragraph N/A PWS Paragraph 4.1.2.1.3

Question: Are shipping costs to AAS and AAAF for the LISC OM&S and other support contractors Government funded? Please provide historical workload data and future expected workload to support these external contractor cargo shipments.

ANSWER: Yes, the shipping cost for all other government support contracts are government funded. Additional information not currently available.

59) RFP Section PWS Paragraph N/A PWS Paragraph 4.1.2.3.1

Question: Please clarify what the "Mission Support Communications aircraft" is referring to. Is there a Mission Support Communications function provided by this aircraft that is the responsbility of the ROS contractor?

ANSWER: PWS clarified.

60) RFP Section PWS Paragraph N/A PWS Paragraph 4.1.3

Question: Reference to "AAF" appears to be in error and should be "AAAF".

ANSWER: PWS corrected to AAAF.

61) RFP Section PWS Paragraph N/A PWS Paragraph 4.1.4

62) RFP Section PWS Paragraph N/A PWS Paragraph 4.1.5

63) RFP Section PWS Paragraph N/A PWS Paragraph 4.1.5

Question: Please clarify if "Airfield Operations and support" are required at both AAS as well as AAAF. If this support is required at AAS, what specific tasks are required as the tasks identified appear to be very broad and encompassing. Please clarify.

ANSWER: AAAF is full airfield ops. AAS is only baggage transport to the air station. However, in very rare cases mutual aid may be requested by the Antiguan Government.

64) RFP Section PWS Paragraph N/A PWS Paragraph 4.1.6

ANSWER: PWS corrected.

65) RFP Section PWS Paragraph N/A PWS Paragraph 4.1.6

Question: Task states, "supports ER including AAS and AAF unless otherwise noted".

Is this meant to imply that the tasks identified in 4.1.6 include all ER locations, or is it meant to imply that these tasks apply to "only" AAS and AAAF unless otherwise noted?

ANSWER: PWS paragraph clarified.

66) RFP Section PWS Paragraph N/A PWS Paragraph 4.1.6.1.1

Question: Task states, "…shall coordinate with LISC OM&S contractor for vehicle and operator support to meet mission requirements.".

- Will the LISC OM&S contractor be providing vehicles for the ROS contractor?

- Does this imply that the LISC OM&S contractor will be providing vehicles at all ER locations to include PAFB, CCAFS, Malabar, JDMTA, AAS, and AAAF? Please clarify.

ANSWER: 1. No. ROS provides vehicles to the OM&S contractor at Ascension and Antigua only. 2. No.

67) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.1.1

Question: Task Note refers to demarcation up to the last patch panel before the base backbone. Can to Government provide diagrams showing demarcation lines of responsibility at all locations? With commercial demarcations and LISC OM&S contractor demarcations, it is critical that the ROS contractor fully understand where lines of responsiblity begin and end.

ANSWER: Comm diagrams provided in Bidders Library.

68) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.1.2

Question: Who does the ROS contractor coordinate with to request communication circuits? Is there another contractor or Government function at CCAFS that provides this? Or is the ROS contractor expected to coordinate with commercial and/or DISA for circuit requests?

ANSWER: At CCAFS from the OM&S contractor. AT AAS and AAAF ROS contractor defines and provides comm. Circuits to the OM&S contractor and USG personnel.

69) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.1.3

Question: Please clarify "the contract shall provide support to theOM&S contractor…".

What is the required support?

ANSWER: Comm support as specified at paragraph 5.1.1.3

70) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.1.5

Question: Task describes Voice Mail support (system administration, operations, and maintenance) at CCAFS, Malabar, JDMTA, AAS, and AAAF locations. Please provide additional detail on the voice mail systems in place at these locations (manufacturer, model, current software versions, etc.). Please clarify what level of support is required at these locations.

ANSWER: Additional info provided in Bidders Library

71) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.2.1

Question: Task states that the ROS contractor "shall utilize the Action Request System (ARS)…". Please clarify what is meant by "utilize" the system. Is the ROS contractor responsible for providing system administration or any other level of support to the system?

ANSWER: Inputs and updates to corrective actions only. SCS manages the

ARS.

72) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.2.2

Question: Is CIPS/WOMS access available at all ER locations to include CCAFS, PAFB, Malabar, JDMTA, AAS, and AAAF? Please clarify.

ANSWER: Yes this is network based. See Software Data Dictionary on Bidders Library.

73) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.2.2

Question: Is the Remedy ARS system in use at any of the ER locations? If so, where?

If not, are there any plans for this system to be utilized at these locations as the AFNETOPS integration continues? What is the timeline for such migration and will personnel training be Government provided?

ANSWER: Available at all ER locations.

74) RFP Section PWS Paragraph N/A PWS Paragraph Table 5-1

Question: Please clarify the difference between tables 5-1 and 5-2 and where these response and completion times apply.

ANSWER: Table 5-1 defines Communications Requirements Response and Completion Time Requirements. Table 5-2: defines 30 SW and 45 SW Mission Support Communications Outage Response and Completion Times.

75) RFP Section PWS Paragraph N/A PWS Paragraph Table 5-1

Question: Please clarify what "response time" means in regards to telephone/voice response versus on-site presence response.

ANSWER: The time it takes to notify COR and user of a problem.

76) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.2.3.4

Question: Note specifies "WR Only", but states that the ROS contractor "will not be required to manage or respond to the following requirements:…". Please clarify if this is intended to mean that these functions are not required at the WR, but are required at all ER locations.

ANSWER: WR does not require voice and video checks at WR under para

5.1.2.3.4. ER voice and video are required per Section 5.1.

77) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.3.1.3

Question: Please provide status as to WR support services and processes being integrated into AFNETOPS procedures.

ANSWER: See Help Desk functions as defined in this PWS. Status will not be provided.

78) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.3.1.3

Question: Please clarify what is meant by "base network management systems"

ANSWER: Reference PWS Para 5.1.3.1.3 – This is in reference admin support of Mission Support Communication network management systems and servers, routers, and switches in the ROS AOR.

79) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.3.1.4

Question: Please clarify where the secondary PoP is located in relation to other support areas. What is the primary PoP location?

ANSWER: Both are at WR as defined in the PWS by Bldg and Rm.

80) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.3.1.6

Question: Who will operate/manage the 30 SCS NCC during the ROS contract? Is this a contract function or Government provided services. Please clarify if the ROS contractor is to provide the NCC function within the 30 SCS, or it is truly an "interface with" function. What is the role of the ROS contractor in reference to the NCC function?

ANSWER: This is a contractor responsibility as described in the ROS PWS.

81) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.3.1.7

Question: Please clarify "applications servers" versus "application servers"

ANSWER: Applications servers have multiple apps on multiple servers but application servers have multiple servers.

82) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.3.9

Question: Please clarify "DDN" and what this interface requirement is.

ANSWER: Defense Data Network. Comm interface to standard DoD networks through comm. room interface.

83) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.3.1.10

Question: Please provide workload data (historical) and/or future workload expectations for the consolidated help desk services.

ANSWER: Workload information for WR Help Desk provided in Bidders Library, utilize historical information as trend data.

84) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.3.1.10

Question: Please clarify who the customers organizations are and the number of customers that utilize the consolidated help desk.

ANSWER: Workload information for WR Help Desk provided in Bidders Library.

85) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.3.1.10.1

Question: Please provide the planned AFNETOPS integration schedule and when the ROS contract provided help desk is expected to be integrated into the AFNETOPS infrastructure. Also, once the ROS contract help desk is integrated into the AFNETOPS infrastructure, will there be any requirement for a local help desk supporting WR?

ANSWER: See Help Desk functions as defined in this PWS.

86) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.4

Question: Are the VESS services currently provided by the 30 SCS support contractor or by another support function (i.e., CES or SFS)?

ANSWER: 30 SW range support contractor.

87) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.4.2.4

Question: Are FOIDS replacement costs government funded or are they contractor provided?

ANSWER: GFP.

88) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5

Question: Task states "this task support both ER and WR unless otherwise noted", but the sentence that follows states "The contractor shall design the 45 SW CITS networks to include all servers, networking equipment, NCC internal cable infrastructure, and spares". This appears to be in conflict with tasks indentified in the PWS as it doesn't appear the ROS contractor is responsible for any of the 45 SW (PAFB) IT support functions. Please clarify what the ROS contractor is responsible for in regards to the 45 SW CITS as well as 30 SW requirements.

ANSWER: 45 SW network design and at the 30SW support of NCC.

89) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2

Question: Please clarify if database administration and development activities are required at all ER locations (CCAFS, PAFB, Malabar, JDMTA, AAS, AAAF).

ANSWER: Yes, as part of a network distributed, centrally managed, database system.

90) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2

Question: Please clarify the database server configuration (locations, quantity, etc.)

where the ROS contractor is to provide DBA related services.

ANSWER: IT equipment configurations provided on comm. Diagrams on Bidders Library.

91) RFP Section PWS Paragraph N/A PWS Paragraph Table 5-2

Question: Please clarify the scope of response and completion times for this table. Is this intended to provide response and completion times in reference to database administration and development functions?

ANSWER: See PWS Paragraph 5.1.5.2.1.3. The contractor shall implement updates to Government systems on the network while de-conflicting updates with on-going user operations and minimizing risk of disrupting service.

92) RFP Section PWS Paragraph N/A PWS Paragraph Table 5-2

Question: Please clarify what constitutes "response time". Is response satisfiled with verbal/telephone response? Or on-site response?

ANSWER: Response is notification via best available method.

93) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2.3

Question: Are system backup devices and consumables (tapes) government or contractor provided?

ANSWER: GFP.

94) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2.4

Question: Please clarify how this task applies to the paragraph 5.1.5 Database Administration function. This appears to be misplaced in the PWS.

ANSWER: This is not misplaced.

95) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2.5

Question: What is the "approved software" currently approved by the government used in the development, maintenance and operations of web-based pages?

ANSWER: Provided in Bidders Library in Software Data Dictionary and in current STIGS.

96) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2.5

Question: Please clarify what "functional systems" are and what the support requirement is. This implies there is a requirement to maintain non-functional systems.

ANSWER: Functional systems are those operating. Non-functional would require contractor to perform maintenance to return them to functional status.

97) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2.6

Question: Please clarify what is meant by "NCC managed systems". Is this referring only to database systems since this is with paragraph 5.1.5.2? Or are there other systems this is referring to as well?

ANSWER: This is WR only as defined in the PWS Help Desk description.

98) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2.8

Question: Is the ROS contractor required to maintain baseline hardware and software configuration for all WR and ER locations and for all hardware and software? Please clarify the areas of responsiblities and locations this requirement applies to.

ANSWER: Areas of Responsibility provided in Bidders Library in comm. Config package.

99) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2.10

Question: Please clarify if it is the Government's intent for the ROS contractor to have an on-site individual at PPAFS and JDMTA. Does this requirement imply the ROS contractor will have a full-time person at these locations?

ANSWER: No. Support as required by the PWS.

100) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.2.10

Question: Please clarify where "Pillar Point Air Force Station (PPAFS)" is located and what functions the ROS contractor is expected to provide at this location.

ANSWER: PPAS has been deleted from the PWS for ROS.

101) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.5

Question: Is this support for the "Public Portable Address (PA)" or "Portable Public Address (PA)". Please clarify.

ANSWER: PWS corrected.

102) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.5.2

Question: Task references "…all requested equipment…".

- Please provide workload data (historical) or expected future events per month/year for these setups.

- Is equipment Government furnished or contractor furnished?

ANSWER: 1. CCAFS -- several per month. 2. GFP.

103) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.6.1

Question: Task references "…physically separated redundant backups for the SAN." Is the separate backup location on or off-base? Is the secondary back up location Government or Contractor provided?

ANSWER: Off base at USG designated location.

104) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.6.1.1

Question: Please clarify what is meant by "data warehouse for all data housed on the 30 SW Mission Support Communications Networks utilizing the integrated Data Management System"

- Is it the Governments intent that the contractor provided IDMS be a data backup system for all data on the network? Please clarify.

ANSWER: 1. Data warehouse is a virtual storage of data. 2. No IDMS will back up the data it produces only.

105) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.6.1.4

Question: Is the requirement for the ROS contractor to establish an NCC for all 30 SW Mission Support Communications Networks outages or is there a separate entity providing 30 SW NCC services? Who is the 30 SW coordinating activity for outages?

How is the AFNOSC involved with these types of activities?

ANSWER: 1. Yes the ROS contractor provides 30 SW NCC function per the PWS para 5.1.5. 2. 30 SCS 3. AFNOSC is the Primary Help Desk for problem documentation and resolution.

106) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.6.1.5

Question: Please clarify "Base CFP" and how is this involved with network outages and restoration actions?

ANSWER: Base Comm Focal Point is 30 SCS – who manages the 30 SW network

107) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.7

Question: Please clarify if the Network Security task applies to ALL 30 SW and 45 SW locations to include downrange locations.

ANSWER: All locations under ROS responsibility.

108) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.7.3.1

Question: Please clarify if the Network Security tasks apply to ALL 30 SW and 45 SW networks as stated in this paragraph, or if these tasks only apply to the networks under the control and management of the ROS contractor.

ANSWER: ROS contractor area of responsibility only.

109) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.8.2

Question: Please clarify the differenence between "mission and mission support communications systems". Is the intent for the ROS contractor to install, repair and troubleshoot mission systems, or just mission support communications systems?

ANSWER: Mission Support Comm. and Mission Communications are defined in the PWS.

110) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.8.2

Question: This task appears to pertain to the "installation, repair and troubleshooting", yet paragraph 5.1.5.8 is titled "Cable Records". Additionally, Q&A's released on November 6, 2013 stated, "The ROS contractor is the central GIMS manager and updates all cable plant records in the central GIMS database.". This does not clarify "where" this function applies to. Please clarify where this GIMS management task is to be peformed by the ROS contractor and where the demarcation points are between the ROS contractor and the LISC OM&S contractor. Does the ROS contractor have circuit records management responsiblity for all of Vandenburg AFB, Patrick AFB, CCAFS, Malabar, JDMTA, AAS, and AAAF?

ANSWER: (AAS and AAAF) Cable Records - Only ER DBOS on mission support (admin) side of demarc points (PWS para 5.1.1.1) downrange.

111) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.8.3.2

Question: Is the 45 SW GIMS system accessible via network at downrange sites or is there a separate GIMS implementation at each downrange site? Please clarify how downrange sites access the 45 SW GIMS.

ANSWER: Networked application. Centrally managed at PAFB.

112) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.5.8.3.3

Question: What is the "government-provided tool"? Please clarify if this is referring to GIMS or a separate tool/system.

ANSWER: GIMS is GFP.

112) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6

Question: What is "…the applicable government provided electronic system…"? Is this referring to the 45 SW GIMS system or a separate system?

ANSWER: PWS clarified.

113) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6

Question: The PWS is unclear where the ROS contractor is responsible for updating CSIR drawings. Please clarify that the ROS contractor is responsible for "ALL" ER CSIR drawing support to include CCAFS, PAFB (except for telephone circuits), Malabar, JDMTA, AAS, and AAAF.

ANSWER: The PWS is correct as written.

114) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.2.1

Question: Please clarify "...design, develop..." in regards to GIMS. The PWS implies that the 45 SW GIMS system already exists.

ANSWER: GIMS exists but may require upgrades or enhancements based on mission support requirements.

115) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.2.1

Question: Please clarify "…enhance a web-based Mission Support Communications tool…".

- Does this web-based tool already exist?

- What web platform is this hosted on?

ANSWER: 1. Yes. 2. Microsoft based. See Software Data Dictionary in Bidders Library.

116) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.2.2

Question: Please provide workload data (historical) and/or future workload expectations for GIMS utility development.

ANSWER: Not available.

117) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.2.3

Question: Please clarify what is being refered to as "…disparate systems."

ANSWER: Disparate would indicate other than GIMS devices such as user workstations.

118) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.2.4

Question: Does the Government provide a separate, off-network, GIMS test and integration capability? Please clarify how testing of new software prior to integration into GIMS occurs.

ANSWER: No. Determined by the ROS contractor.

119) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.2.5.2

Question: Please clarify what is meant by "The contractor shall not interfere with Range operations".

ANSWER: No direct Range Ops interface allowed at Range Control Center or Prime Mission Equipment.

120) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.2.5.3

Question: Please clarify if this is intented to state "data are synchronized" versus "infrastructure are synchronized".

ANSWER: PWS language will be clarified in next update.

121) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.3

Question: Where is the 45 SW Enterprise GIS system located? Is this at PAFB, CCAFS, downrange locations?

ANSWER: PAFB is the server location with clients at sites as required.

122) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.3.3

Question: Where are the GIMS PM and GeoBase PM located and what organization do these individuals belong to? (CES? SCS?)

ANSWER: GIMS option in GIS is managed by 45SCS at Patrick AFB and 30SCS at Vandenberg AFB. GeoBase is a GIS option managed by 45CES at Patrick AFB and 30CES at Vandenberg AFB. See Software Data Dictionary in the Bidders Library.

123) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.3.8

Question: What is the role of the "government Database Analyst" and what is the interface requirement with the ROS contractor System Administration function? Is this to be a daily interaction or ad hoc interaction? Do the System Administrators need to be physically located near the Analyst?

ANSWER: The government Database Analyst Provides support and analysis of database products. Interaction as required to maintain database integrity.

Physical location at ROS contractor discretion.

124) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.4

Question: Task references "Table 5-6" for "applicable priority". Table 5-6 is missing.

Please clarify.

ANSWER: PWS typo. PWS corrected.

125) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.5

Question: What is the "…government-provided tool…" used to update, upgrade, and maintain existing CSIR drawings? Please clarify.

ANSWER: The GIS or GIMS web based app.

126) RFP Section PWS Paragraph N/A

Question: Since this section pertains to GIS System Administration, is it the Government's intent that the System Administration function will be performing the update, upgrade, and maintaining the existing CSIR drawings? Please clarify.

ANSWER: Yes.

127) RFP Section PWS Paragraph N/A

Question: Task reference maintaining existing CSIR drawings for supporting Mission Support Communications "and" mission systems "and" facilities. Please clarify what mission systems this is referring to and at which locations this is required.

ANSWER: Comm transport utilized by mission comm up to the demarc point.

128) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.6.5.2

Question: Please provide workload data (historical) and future expected workload required to support the drawing and CSIR updates for 45 SW as note in this task.

ANSWER: This information will be provided at next Bidders Library update.

129) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.7.2

Question: Please clarify if the 45 SCS (PAFB) is the same focal point for coordinating LMR actions for downrange (AAS and AAAF) locations.

ANSWER: Yes.

130) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.1

Question: Please clarify how the 45 CES/SFS operates and manages the 45SW 911 system and at which 45 SW locations this is required. The paragraph notes "(ER Only)", but it is not clear if the maintenance of voice switch, line and end instruments applies to ALL ER locations, if it is just the 911 system portion of the telephone system, or if it's the entire phone system (except at PAFB) as noted in 5.1.8.

ANSWER: 45 CES manages the 911 system but maintenance is the contractor requirement. Updated info provided in the Bidders Library at next update.

131) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.2

Question: Please clarify where operation and maintenance of the airfield primary and secondary nets and crash stations is required. The paragraph notes "(ER Only)", yet the paragraph also states specifically CCAFS and PAFB as well. Is this support required at any other ER locations?

ANSWER: The PWS is correct as written. Updated tech information provided in Bidders Library at next update.

132) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.5

Question: Please confirm locations where the ROS contractor is required to respond to telephone outages. There appears to be conflict with other section tasks stating that PAFB is not included telephone support, yet this states that PAFB is included. Please clarify.

ANSWER: PWS corrected. That is correct PAFB is not included and is handled by 45 SCS.

133) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.6

Question: Please confirm if PAFB is included in this task requirement. Paragraph 5.1.8 notes that PAFB is excluded, yet this paragraph states that this includes all of ER.

ANSWER: That is correct all of ER except PAFB. See Bidders Library doc Areas of responsibility.

134) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.6

Question: Please clarify if this support is also required at Malabar and JDMTA.

ANSWER: Yes.

135) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.7

Question: Are secure telephone devices considered GFE or contractor furnished?

ANSWER: GFP.

136) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.7

Question: Is the distribution and management of secure telephone devices required at PAFB by the ROS contractor?

ANSWER: No, PWS Clarified.

137) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.8

Question: Does this requirement apply to hardware, software, and firmware modifications, upgrades, testing, and evaluation support at PAFB?

ANSWER: No, PWS Clarified.

138) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.9

Question: Task references Table 5-8 which is missing. Please clarify.

ANSWER: PWS clarified.

139) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.11

Question: Task states, "Contractor shall manage and maintain an annual inventory of telephone equipment and validation of telephone lines. Since paragraph 5.1.8 states, "(This task support both ER and WR unless otherwise noted)", does this task include all ROS contract locations to include VAFB, PAFB, CCAFS, Malabar, JDMTA, AAS, and AAAF? Also, does this task include all facilities at these locations or other specific location/buildings at these locations? Please clarify.

ANSWER: 1. Yes as noted. 2. As noted in Bidders Library Areas of responsibility doc.

140) RFP Section PWS Paragraph N/A PWS Paragraph 5.1.8.12.8

Question: How many hard copies of the telephone directory are required annually?