About this file

This is the final posting of responses to questions submitted in response to the draft RFP posted 23 Nov 10.

Text of this file

SOCOM TACLAN DRFP

QUESTION #
SECTION / PARAGRAPH / PAGE
Questions / Comments

Response

(TBD)

Action

(TBD)

1.
REF All RFP Section B CLINs and RFP Pg. 21, Section F, Deliveries or Performance.
a. Page 21 leaves FOB destination to be identified on each delivery order, TBD, which cannot be adequately priced in advance. Additionally, multiple CLINs also leave any MIN or MAX quantities as Undefined. How does the Government envision offeror’s proposing against undefined requirements on a FFP basis? Will the Government consider providing a baseline quantity value for consistency in proposal preparation and evaluation purposes in the final RFP?

Shipping is to be included in the price of the equipment.

There will be a Shipping CLIN for the additional cost to ship OCONUS.

Numbers will be included in the FRFP for evaluation purposes.

2.

b. Also, how does the Government anticipate offeror’s pricing FOB destination/delivery costs? Would this be proposed separately at the delivery order level, or could SOFSA be used as the focal point for product delivery and property management/inventory control prior to final field deployment?

Shipping will be included in the price for CONUS deliveries.

3.
REF RFP Pg. 63, Section L-3.3. Part IV-D Cost CLINs.
1. The Government has provided an IGCE of $40,000 for Travel. When proposing and populating Section B CLIN data, should the offeror include applicable indirect expenses (i.e., G&A) in the proposed cost for that CLIN (e.g., $42,000 with G&A markup)? Please clarify.

The total shouldinclude $40K plus the indirects.

4.
Technical Support: Please provide more definition of Technical Support as referenced on Pg. 61, Section L-3, Technical Support.
1. Specifically:

a. Is Level 1 Support (Help Desk, phone support, troubleshooting) required?

b. Is Level 2 Support (detailed technical support both on phone and in the field, including Unplanned Depot Level Maintenance (UDLM) and Emergency Depot Level Maintenance (EDLM) support) required?

No – Level 1 Help Desk Support will be accomplished by ITSM (Svc Desk)

Level 2 support will be accomplished by the Distributed Computing Contractor or Specialty Services. If the Level 2 Support contractor is unable to resolve the issue, said issue would be upgraded to Level 3 and assigned to TACLAN Production contractor for resolution.

5.

2. Help Desk: What is the expectation of the Level 1 Help Desk?

a. Are there service level agreements for Help Desk support?

b. Does the Help Desk need to handle ITAR conversations?

c. Does the Help Desk need to handle classified conversations?

There is no Level 1 help desk requirement associated with this contract.

Yes – there are SLAs that address problem resolution on elevated service calls that will impact this contract.

There shouldn’t be any ITAR conversations.

There is no Help Desk associated with this Contract

6.

d. What is the expectation for Level 2 Support for the deployed systems?

e. Will the Contractor be required to provide field personnel for Level 2 Support?

e. Who will determine if/when field support is needed?

f. Are there service level agreements for Level 2 Support?

Level 2 support is covered by Distributed Computing or Specialty Services Contractor.

Same as above.

The SITEC Service Desk is the only function that can elevate service requests to Tier 2 or 3, however, they will make that determination based on inputs from Distributed Computing contractor and the Specialty Services contractor. The TACLAN contractor will determine if they need to dispatch a technician to the field if they determine the Level 2 contractor in the field doesn’t have the capability to support the maintenance action.

See above.

7.
Equipment Repairs
a. What are the projected volume and nature of work for repairs coming back from deployment location(s)?

b. Is there a service level agreement associated with this effort?

There are numerous Monthly Status Reports and Quarterly Warranty and Maintenance Status Reports in the Bidders’ Library which can be used to determine the volume and type of repair and maintenance actions

There is an SLA that addresses timeliness in solving level 3 problems.

8.
Section B Supplies or Services and Prices, B.1 and the TAC LAN PWS Section 3.2, TACLAN Production/Lifecyle Support
Question –Why does the TAC LAN PWS, TACLAN Production/Lifecyle Support, paragraph 3.2 require the contractor to provide five years of lifecycle support starting at acceptance, while the Draft RFP, General Information page 2, Section B Supplies or Services and Prices, B.1 states that this IDIQ will be structured in a 3 year base contract, with two optional one year extensions?

Discussion – As worded, the lifecycle five year support requirement could extend beyond the period of performance (POP) of the contract. The PWS section 3.2 defines lifecycle support to include services that require SIPRNet access and the exchange of information and technical services. SIPRNet access, authority to travel into certain AORs, and facilities by contractors requires a contractual vehicle that will be provided via this contract. Therefore, if the desired 5 year lifecycle support services need to extend beyond the contract POP, such services need to be contractually supported.

Recommendation – Align the PWS lifecycle support period requirement with the contract period of performance or include a line item to cover the cost and necessary security/access authorizations for such services.

The Lifecycle support period has been adjusted.

9.

Question –How will prime contractor work share percentage be calculated on the TACLAN contract?

Discussion – Since the TACLAN contract is a small business set aside, a minimum of %51 of the “work” must be accomplished by the prime contractor. The overall RFP is silent on how this percentage will be calculated.

Recommendation – Include guidance about prime contractor versus team members work share distributions in the final Request For Proposal.

Work share is based on Total Contract Value.

10.
Draft RFP, page 70, Section M, Para: M 3.1.2

Question – How does a contractor gain additional credit, in the technical factor 1 evaluation criteria, for providing an innovative technical approach to the TACLAN proposal?

Discussion – Current evaluation criteria doesn’t provide any additional credit for an offeror to provide an innovative design approach to the TACLAN system. None of the CLINS reference the Attachment 13, TACLAN System Specification which includes target and objective performance requirements. The evaluation criteria coupled with the requirement to deliver existing baseline solutions discourages design innovation. It appears that the Government is requesting that contractors bid the current system.

Recommendation – Explicitly require that the proposed technical solutions meet threshold system level performance requirements as defined in the TACLAN TSS Attachment 13, and add to the technical proposal evaluation factors an innovation factor that rewards solutions that meet or exceed TSS objective performance requirements.

Refer to section L & M of the FRFP for guidance.

11.
Reference – Draft RFP, Section C - Performance Work Statement (PWS) page 22, Para. 10.6

Question – Will the Contractor Asset Management system be provided GFE to the contractor?

Discussion – It is unclear in the PWS if the contractor asset management system is a GFE item or contractor developed product. If it is a contractor developed product, how will USSOCOM accredit the software and add it to the SIPR network.

Recommendation – USSOCOM add this as a GFE item.

Yes, it will be provided.

12.
Draft RFP, Draft PWS, Pg 30, Para 11.0 TACLAN Contractor Information assurance
Question – Will USSOCOM require adherence to DIA and National Institute of Standards and Technology (NIST) standards?

Discussion – HQ USSOCOM IA on the TS/SCI IA level reports to DIA. Therefore, applicable DIA standards should be referenced. National Institute of Standards and Technology (NIST) is becoming a prominent fixture in the IA realm. NIST standards such as NIST SP800-53 will be the replacement for DIACAP.

Recommendation – In this document where DOD and NSA appear applicable DIA and NIST standards should be included. For example: IAW applicable DOD, NSA, NIST and DIA standards.

Yes

13.
Draft RFP, Draft PWS, Pg 31, Para 11.0 TACLAN Contractor Information assurance
Question – What is the Governments meaning of “Minimize and protect trusted systems elements”?

Discussion – It doesn’t make logical sense to minimize and protect trusted systems elements.

Recommendation – Change to read: “ Minimize risk and protect trusted systems elements”.

The language has been removed.

14.
Draft RFP, PWS, Para. 6.1 - Geographic Coverage, Para. 10.13 – Service Delivery Document Management, Para 12.0 – TACLAN Operations Management Support, Para 12.2 – TACLAN ON-Site Technical Support
Question – What is the TACLAN definition of Level 1,2,3 support?

Discussion – In the reference pages and paragraphs, the Government refers to various level of TACLAN contractor support (i.e. Level 1, 2, 3 support and Level 3 reach back support). Nowhere in the draft RFP documentation are these support levels clearly defined.

Recommendation – Government include the TACLAN maintenance conops that provides the contractors with detailed definitions of level 1, 2, 3 maintenance levels.

These definitions can be found in the ITIL v3 documentation.

15.
Draft RFP, PWS, Page 15, Para. 6.2 - Contractor Responsibilities

Page 38, Para. 12.2.2 – Problem Support What is the TACLAN definition of Level 1, 2, 3 technician support and definition of labor category qualifications?

Discussion – In the reference pages and paragraphs, the Government refers to various TACLAN technician levels (i.e. Level 1, 2, 3 technician support). Nowhere in the draft RFP documentation are these support levels clearly defined. Nor is the labor category definitions/qualifications defined.

Recommendation – Government include a maintenance CONOPS that provides the contractors with detailed definitions for level 1,2, and 3 technician task levels, labor category definitions and personnel requirements.

These definitions can be found in the ITIL v3 documentation.

Labor categories are defined in the TEP Matrix.

16.
Draft RFP, Page 62, Para L-3.2.1.2.2
What is the correct PWS Quality Assurance section being referred to in this paragraph?

Discussion – The RFP Paragraph refers to section 9.13 of the PWS for additional definition of quality assurance requirements. Paragraph 9.13 doesn’t exist in the PWS.

Recommendation – SOCOM provide correct PWS section for definition of Quality Assurance requirements.

This will be corrected in the FRFP.

17.
Draft RFP, PWS, Page 16, Para 7.2

Can the prime contractor meet the CMMI requirements of this PWS paragraph, by sub contracting this work effort to a contractor that posses CMMI certification?

Discussion – CMMI certification for many small businesses is not practical. Sub contracting this work may make a better business case for the small business.

Recommendation – Remove requirement for TACLAN prime contractor to have and maintain CMMI level 3 certification. Require all software work to be accomplished using CMMI level 3 processes.

Yes

18.
Attachment 13 TSS section 3.6.1 LAPTOPS
3. Attachment 13 TSS section 3.6.1 LAPTOPS states: The laptop shall minimally comply with:

a. Display/Video: The video card shall have a minimum of 256 megabytes of memory.

This section indicates a Video card with a minimum of 256MB of memory. This would be commonly understood to mean a discrete graphics chip with a minimum of 256MB of dedicated memory as is consistent with the currently approved LAPTOPS.

Attachment 13 TSS section 3.6.1 LAPTOPS goes on to state:

e. Peripherals: Laptops shall have an… integrated Video….

This requirement indicates an integrated Video which is substantially less powerful and not consistent with the currently approved LAPTOPS.

Question: Is the LAPTOP minimally required to have a discrete graphics processor and 256MB of dedicated video memory or is integrated graphics with shared memory the minimum?

Do not use the TSS as the baseline reference document. We are asking for 10.1 baseline in accordance with Attachments 1 through 6 and Attachment 19

19.
DraftRFP Section L-1.1
L-1.1 The purpose of this procurement is to provide TACLAN Full Suites, C2 Suites, and FCDs in accordance with the current approved baseline release (Attachments 1-6). Furthermore, the offeror shall provide C-LAN Kits, MPKs, RoiPs and FMVs in accordance with Attachments 7 – 10 and the Technical System Specification (TSS). No deviations from the current approved baseline release or equipment list are permitted.

Question: By stating that “no deviations from the current approved baseline release or equipment list are permitted” are you setting in stone such vendor specific devices as the Panasonic CF-52 Laptop thereby preventing healthy competition and potentially risking protests, or are will other COTs LAPTOPS that meet or exceed the current LAPTOP specifications, while potentially offering a lower cost of ownership, be considered?

Additional Question: With reference to Draft RFP Are the TACLAN Full Suites, C2 Suites and FCDs also needing to be supplied in accordance with the TSS?

We are asking for the 10.1 baseline. There is an opportunity for technology insertion after the initial order of suites.

Do not use the TSS as the baseline reference document. We are asking for 10.1 baseline in accordance with Attachments 1 through 6 and Attachment 19

20.

The NAICS Code listed for this RFP is 541519 “Other Computer Related Services” or “Information Technology Value Added Resellers”, with size limits of $25M and 150 employees respectively. Due to the large TACLAN work scope which includes equipment production, software development, and maintenance, would the Government consider specifying an NAICS Code such as 334290 to allow larger small businesses with up to 750 employees qualify for the small business set aside? The use of NAICS Code 334290 would increase the pool of qualified small business bidders and open up the competition to small businesses with the resources needed to successfully execute the TACLAN program.

NAICS Code 541519 is the proper code for this procurement.

21.
PWS
Page 7, Paragraph 3.2 states “The TACLAN contractor shall provide TACLAN Family of Systems equipment in accordance with the currently approved baseline and paragraphs 4-11 and 16 of this PWS.”

There is no Paragraph 4-11, and Paragraph 16 describes a training requirement.

Please clarify the reference to these two paragraphs.

That is paragraph 4 thru 11 and paragragh 16. The paragraph numbers and references will be updated in the FRFP.

22.
Page 62, Paragraph L-3.3.1.2.2 Quality Assurance
Paragraph L-3.3.1.2.2 Quality Assurance requires the offeror to provide evidence of having a minimum ISO Certification of 9001:2000.

Although 9001:2000 certification is customary in many companies today, quality management processes, like many business processes, have evolved with experience and use. Industry recognized improvements were implemented in the more recent standard ISO 9001:2008. Most companies that are in the forefront of quality management have already been certified under the new standard.

The 9001:2008 standards established numerous changes required to keep pace with changes in technology and to update the feedbacks and responses to surveys that were gathered over the last years from those operating under the earlier standard. Among the many areas to the existing requirements of ISO 9001:2000 that have been clarified by the changes, and particularly important to this contract - and now required by 9001:2008 include:

· Documentation

· Management Representative

· Competence

· Information systems

· Customer Requirements

· Customer Satisfaction

· Process Monitoring and Measurement In order to provide the SOCOM with the highest quality of equipment and services, it is strongly recommend the minimum quality standards for this procurement be raised, and that the RFP be updated to ensure offerors are certified ISO 9001:2008.

The requirement will remain ISO 9001:2000.

23.
Page 64, paragraph L-5,
Page 64, paragraph L-5, requires the offeror to submit the names of 13 personnel who poses a Top Secret/SCI clearance.

What is the rationale for the quantity 13? Does SOCOM have a pre-identified need for 13 specific skill sets? Possibly types and locations are required that aren’t identified elsewhere in the RFP? Are these 13 to be located at our production facility in Tampa?

The number has been removed. We are asking you to define your key personnel.

24.
Page 9, Paragraph 4.2
The Contractor will require access to the Non-Secure Internet Protocol Router Network (NIPRNET), the Secret Internet Protocol Router Network (SIPRNET)….and SIPRNET access at the Contractor facilities.”

Will the requirement for SIRPNET access be necessary at contract award date? If not, what will be the grace-period for the Contractor to obtain the capability?

SIPR access will be provided at a Government facility until it is installed in the contractor facility.

25.
Page 10, Paragraph 5.0
“Each unit in receipt of a TACLAN suite will be responsible for the installation, configuration and execution in such a way that it complies with the USSOCOM DAA Type Accreditation.”

This paragraph leads the Contractor to believe that unit will give the Contractor guidance for installing and configuring the TACLAN Suites. Is this the manner in which the sentence should read, or is will the Contractor provide recommended solutions installing and configuring the systems?

The contractor will ship the TACLAN suite to the unit and provide New Equipment Training (NET) to the unit. Part of NET is how to properly set up and connect the suite.

26.
Page 12, Paragraph 5.2
Page 12, Paragraph 5.2 states, “In support of these SLAs, the TACLAN Contractor shall work openly and cooperatively with the ITMO and other IT service providers to ensure that all SOCOM TACLAN production systems….Primary interactions with other providers will include the SITEC Service Desk, Distributed Computing, and Data Center Providers.”

The PWS briefly summarizes the SITEC IT Service Areas; however, how in-depth does the government expect the Contractors to write to convey an understanding of how the TACLAN Contractor will interact with each Service Area Offeror should communicate their understanding in how the other applicable SITEC towers will participate in service call resolution, integration & testing, and fielding/training.

27.
Page 23, Paragraph 10.8
Page 23, Paragraph 10.8 states, “The TACLAN Contractor shall perform all TACLAN Configuration Management activities for all TACLAN equipment and software until delivery, which shall be performed in accordance and compliance with USSOCOM’s enterprise-wide configuration management policies and procedures.

Where are the policies and procedures located? Question number 3 also applies to this requirement.

All available USSOCOM policies and procedures have been included in the SITEC Bidder’s Library.

28.
Page 26, Paragraph 10.12.1
What is the definition of the SIF?
SOF Integration Facility
29.
Section F – Delivery Location and Schedule

Please clarify what determines “delivery” as defined in this section. Does delivery constitute when suites are completed and ready for shipment or is delivery when a suite arrives at a final destination?

Delivery is when the equipment unit is received at final destination unless the contractor was asked to delay shipment of the completed prpoduct..

30.
Section L 2.1 Page Count

L 2.1 states Page size shall be 8-1/2” X 11 with the exception of illustrative foldouts, which shall not exceed 11 x 17 inches. Foldouts will count as two pages. L 2.2 states Pages that are predominantly drawings or graphics will be counted against the page count limitation.

If an 11x17 foldout is a graphic/drawing, does it still count as 2 pages against the page limitation?

Is a table/matrix treated as graphic/drawing or text against the page limitation?

What are the pricing requirements for the prime when utilizing subcontractor cost data?

Any page where drawings or graphics cover at least three quarters of the area of the page will not be counted against the page count.

A table/matrix will be counted as text.

FAR requires the prime to perform a price/cost analysis on the subcontractor's proposed cost/price to determine price reasonableness. If the subcontractor will not allow access to their records, the subcontractor should submit their cost proposals directly to the Government and we will complete the analysis.

31.
L 3.3 Past Performance Information Sheets

Bullets number 7 and 9 are word for word duplicates and bullets number 8 and 11 are word for word duplicates. Does the government intend to delete the repeated entries for the final RFP?

Section L 3.3 appears to not allow the use of subcontractors past performance:

Reference Data and Relevant Experience.

Contents. The Offeror shall submit a Past Performance Proposal containing the following:

2. Summary Page describing the role of the Offeror and each subcontractor, teaming partner, and/or joint venture partner Past Performance Information Sheets.

1. The Offeror shall submit a maximum of five Past Performance Information Sheets identifying active or completed contracts, either Government or commercial and include as applicable the names and work involvement of any of the Offeror’s proposed 3rd party team members.

2. The Government defines “recent” as contracts that have been performed during the past three years from the date of issuance of this solicitation.

3. The Government defines “relevancy” as how closely a past performance reference compares to USSOCOM’s support requirements in regards to overall organizational size, technical scope, geographic complexity, and extent of the services provided by the Offeror to the reference customer.

If the team’s construct is intended to provide USSOCOM the best demonstration of relevant demonstrated past performance, it would appear the use of the Offeror’s overall team evaluation should be considered.

They have been removed.

Subcontractor past performance can be used.

32.
Section M

Factor 2 Subfactor Numbering

M 2.1.1 lists Program Management Approach as FACTOR 2, with the subfactors numbered as follows:

· Subfactor 3A – Delivery Schedule

· Subfactor 3B – Quality Assurance M 3.1.3, the evaluation approach for the subfactors within FACTOR 2, lists

· Subfactor 2A – Delivery Schedule

· Subfactor 2B – Quality Assurance Does the government intend to clarify or re-align the numbers of the subfactors?

The Factors will be updated in the FRFP.

33.
Version Description Document (VDD) Comments and Questions:

1.1 of the VDD refers to a FILO Laptop Server which appears to be a laptop version of the Full Suite. However, 1.2 of System specification refers to the TACLAN system consists of: “Suite, Mission Planning Kit (MPK), Field Computing Devices (FCD), Video Distribution Hub -Lite (VDH-L), Coalition Local Area Network (C-LAN) and Radio Over Internet Protocol (ROIP) Kit.”

Is the FILO Laptop server part of TACLAN? If so, what and where are the full specifications for this component?

Yes, It is an 8GB RAM version of the CF 52.

34.
Operations & Maintenance Comments and Questions

2.2.8 – Help Desk

The Help Desk currently provides replacement parts within a 24-hr timeline. This could be difficult for an OConus site, as they normally have minimum two day turn around. Need to validate against any SLAs for this type of support.

Throughout the attachment (i.e. Para 10.5), there is reference to TACLAN Help Desk. Will the Help Desk be performed under the ITSM tower within the combined Help Desk?

Help Desk functions will be accomplished via the SITEC Help Desk. The TACLAN contractor will perform tier 3 support.

35.
2.2.11 – Special Privilege CAC

2.2.11 states that username/passwords are used to logon. Under current DOD policy use of a CAC card is required without special exceptions. Because all Administrators require a “special privilege” CAC, this may pose a problem and therefore have granted exception to TACLAN users. Team NDS would like to verify this requirement.

HBSS is provided by SOCOM. Is this system required to be managed, maintained by the TACLAN team or will this require an ACA with another vendor for management/monitoring?

The administrator would use an Administrator user-name and password.

The HBSS is part of the baseline to be managed by the TACLAN contractor.

36.
Install Manual Comments and Questions

1.4 – Method of Installation Section 1.4 references a USB bootable hard drive. Is this the preferred method of installation? Based on the current security posture throughout the DOD, will this continue to be the preferred method?

Yes to both questions.

37.
3.1 – Servers on Laptops

Section 3.1 discusses building a server on a laptop. This appears to be the focal point for many other actions in building the TACLAN suites as many administrative actions are derived from this. Not an issue, but something to be aware of moving forward.

Noted

38.
3.3 – Virtual Machines
3.3 Does the TACLAN suite run 10 virtual machines over the entire suite or are there ten virtual machines per computer system. In a failover situation would we need to support 20 machines on a single system?
TACLAN virtual machines are deployed seperatelt over three segments: NIPR, SIPR, JWICS.

In the 10.1 baseline the segments will have different requiements in terms of virtual machines.

The TACLAN does not run 10 virtual machines per segment.

Failover/disaster recovery requirements are based on the number of VMs deployed by segment. The remainig server still needs to run only ten VMs

39.
C-LAN Comments and Questions

Container COMSEC MFG: General Dynamics Product Name: TACLAN

MFG SKU: KG-175

Description: This is a full size TACLAN device. Description requests: includes a five-year (5) warranty for the TACLAN Micro only and technical help desk support.

Remedy: MFG SKU KG-175D Is the request for a TACLAN- MICRO support an error or the product SKU an error?

It should read KG-175D

40.

Should we quote training in both CONUS and OCONUS?
Yes

41.

What are the contractor facility requirements, i.e. size, warehousing, clearance level, safeguarding level, secure/unsecure network connectivity, etc.?
The facility size is up to the contractor.

The facility is TS and the storage is Secret.

SIPR will be required.

42.

What are the system requirements for Material Control and Maintenance Data Collection?

Will this be a Government furnished or Contractor furnished system?

The Asset Management System will be GFE.

43.

Is the SIE Standard Trouble Ticket and IT Service Management system SSAVIE?
No - BMC Remedy on SIPR.

44.

Sec 3.2 Subsection d and e seem to be inverted. Please clarify.
That has been corrected.
45.
System Specification Comments and Questions
Regarding redundancy and fault tolerance, are there more detailed power system specifications for servers, storage, and networking hardware?
The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.
46.
1.2 – ROIP Kits
The ROIP Kit is described and in attachment 10 the ROIP Kit parts list is provided. Can you provide us with a set of drawings that details how they want the RoIP chassis built? We need the physical layout of where the individual parts are located and a wiring diagram of how these parts are connected together.
Elevation drawings will be added to the Bidder’s Library.
47.
3.1 - Boundary

3.1.1.2 (e) states that the WAN equipment must support IGRP (Interior Gateway Router Protocol), and section 3.5.3 (c) states that the LAN equipment must also support IGRP. IGRP is a Cisco proprietary protocol. What is the intent of this requirement? Is there a requirement that only Cisco router and switch equipment can be proposed?

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

48.

3.1.2 states there is an objective to have the TACLAN boundary equipment provide Cross-security Domain Systems (CDS) capability for NIPRNET to SIPRNET or SIPRNET to JWICS user data traffic. Can you provide specific information on what the boundary hardware and/or software is required to do when passing traffic between the security domains?

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

49.
3.3 - Servers

3.3 (d) states “Within each segment the virtual infrastructure shall provide consolidated backup”.

Question: Is this referring to the software product “VMware consolidated backup” specifically, or does it refer to a general central backup strategy. Detail more specifically what constitutes a consolidated backup strategy.

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

50.

3.3.1 (b) states “Hard Drives shall be externally removable storage, compliant with security requirements associated with classified operations.” What does this mean? Detail out each of the components of this requirement: a) what constitutes “externally removable?” (In rack? Off the front/back?) b) what constitutes compliant with security requirements? Does this include on non-secure segments? Is there a specific regulation or standard to adhere to?
The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

51.

3.3.1 (b) states “The drives shall be of sufficient size to run all of TACLAN’s software applications.” If servers are virtualized, and applications are virtualized within virtual machines that reside on external storage, explain the purpose and usage of the internal storage?
The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

52.

3.3.1 (e) states “All servers shall have DVD/CDROM drives. Does this DVD/CDROM drive have to be integrated in the server, or can it be externally connected? How does this compare to the numerous references to software installations via USB drive mechanisms throughout the RFP?
The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

53.

3.3.1 (f) states “All servers shall have a minimum of two (2) Peripheral component Interconnect Express (PCI-E) slots.” Can the usage scenarios of these slots be enumerated? What is the general purpose of having these slots?
The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

54.

3.3.3 – KVM

What devices are/will be connected to the KVM?

Is a KVM required for each stack (SIPR/NIPR/JWICS) or just available for low level server access since VMware is required on the servers?

Describe how the KVM will be used.

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

55.
3.4 - Storage

3.4.1 states “This mass storage device shall support all file systems and protocols supported by client and servers.”

Given the fact that portions of the software installed on clients and servers is GOTs (and classified), can a specific table defining all required file systems and protocols be provided?

If not, can some better specification be placed around what is to be/not to be supported?

Is the reference to NIPR, SIPR and JWICS correct in sections 3.4 and 3.4.1?

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

56.

Section 3.4 states that TACLAN shall provide additional storage externally to the servers. This storage will be used for backup and user data storage. For SIPRNET and JWICS, storage shall consist of two (2) separate storage devices; one for primary storage of user data and backup; the second for near-real time replication and redundancy. For NIPRNET, storage will consist of one (1) storage device for primary storage of user data and backup.

Section 3.4.1 states that the user storage data partition shall have a minimum capacity of five (5) terabyte (TB) (Threshold) ten (10) TB (Objective) of usable storage for NIPR and JWICS. The user storage data partition shall have a minimum capacity of ten (10) terabyte (TB) (Threshold) twenty (20) TB (Objective) of usable storage for SIPR, It shall be provided to support online data storage and archiving at all levels of classifications. This mass storage device shall support all file systems and protocols supported by the clients and servers. All storage media shall be removable.

What kind of backup software does TACLAN own?

What does for near-real time replication and redundancy mean?

What network bandwidth does the network have and what distance does the the data need to be replicated?

Does TACLAN require MDL SAS drives or SAS drives?

What are the key applications that will be running on the SAN storage?

Does TACLAN want Data Deduplication to be part of the proposed backup solution?

Will TACLAN accept a D2D device as a backup target or will TACLAN require tape?

Will TACLAN require a specific CERT for their SAN storage?

Will TACLAN require Fibre Channel?

Will TACLAN require IPv6?

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

57.

Does TACLAN want Data Deduplication to be part of the proposed backup solution?

Will TACLAN accept a D2D device as a backup target or will TACLAN require tape?

Will TACLAN require a specific CERT for their SAN storage?

Will TACLAN require Fibre Channel?

Will TACLAN require IPv6?

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

58.
3.6 - Computing

3.6 states “TACLAN includes specific computing devices that may interface with all three (3) TACLAN segments…” Is the requirement for these devices to be able to interface all three network segments simultaneously?

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

59.
3.6.1- Laptops

Will 15.6” be considered a non comply?

Is a USB to Serial adapter acceptable?

Are PCIe slots required in notebook? (Not available in notebook, only in dock) Is there a required processor speed?

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

60.
3.6.2 - Field Computing Devices

What is the minimum and/or maxim weight requirement?

Is a 12.1” display acceptable? Spec calls for 10.4.”

Is a USB to Serial adapter acceptable?

Is an ExpressCard to Serial adapter acceptable?

Are PCIe slots required in notebook?

Is a semi rugged notebook inside an Otter ruggedized case considered to be a fully ruggedized device?

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

61.

Question: Regarding the current Software Baseline, Windows 7 Professional with Downgrade rights to Windows XP Professional is End of Life. Manufacturers of the LAPTOP and FCDs are not able license the Windows OS in the manner prescribed in the RFP but may only invoke downgrade rights from Windows 7 to Windows Vista. Has the government verified with Microsoft that it can obtain and deploy this particular license for some or all of the contract delivery period? If not, will the government be negotiating with Microsoft for any special licensing necessitated under this contract prior to the contract delivery period?

The Command’s Microsoft EA agreement provides extended end of life support for XP beyond what is provided to other consumers, however it is anticipated that we will upgrade to Windows 7 at some point during the contract period.

62.

Now that Windows XP Professional is end of life what is the TACLAN plan for migrating to a currently supported version of Windows such as Windows 7 Professional?
Same as above

63.

Not withstanding any special licensing arrangement negotiated between the LAPTOP or FCD manufacturer and Microsoft, at present the only commercial offering of Windows XP Professional is through the Microsoft Embedded Systems group. LAPTOPS and FDCs licensed and produced with Windows XP Professional Embedded would not include upgrade rights to Windows 7 Professional. If this should be the only means of legally licensing Windows XP Professional on LAPTOPS or FCDs would this be acceptable to the Government?
Yes

64.

Regarding the current Hardware Baseline, there is known to exist a competing COTs LAPTOP. The specifications were purposely modeled to meet or exceed the specifications of the Panasonic LAPTOP in use for the TACLAN as of Q1-2010. The device meets or exceeds all known suitability requirements. It is has one less external USB but TACLAN it has been verified that there are rarely any attached USB peripherals in use. 4 USBs are never used concurrently. It provides 1920x1080 resolution – same as the vast majority of TACLAN LAPTOPS previously deployed instead of 1920x1200 as called for. REASON: 1920x1200 panels are EOL, extremely difficult to obtain and being replaced by 1920x1080 which are in far greater supply, offer newer technology, not subject to chronic availability shortages, more competitively priced, and offer greater value. This allows the use of a superior LED backlit screen versus the CCFL backlight, resulting in better power efficiency, greater brightness, and better value. Virtually all of the other specifications of our LAPTOP have been validated against the current TACLAN v 10.0 Baseline. Will the government consider such a LAPTOP or is strict adherence to Attachment 2, Appendix A, “A20 – Panasonic Laptop Computer” required which will almost assuredly cause the government to pay a huge “Panasonic ONLY” premium? Would the government consider easing the specification ever so slightly to 1- eliminate the IAW Attachment 2 from the requirements of CLIN 0001, 0007, 0008, 0011? Would the government consider easing the requirement of 4 USBs to 3 USBs? Would the government consider easing the requirement from 1920x1200 to 1920x1080 which is already in widespread TACLAN usage and performing well? Is “LED backlight” with the numerous associated advantages worth specifying?

We are asking for the current laptops.

There will be an opportunity for technology insertion at a later date.

65.

Although not officially part of the DraftRFP requirements, confusion is created by Attachment 13. Is “Discrete Video Processor with a minimum of 512MB of dedicated Video Memory” a better way to state the requirement described on Attachment 13 section 3.6.1? What is the effect of the TSS section 3.6.1 on CLINs 0001, 0007, 0008, and 0011?

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

66.

The DraftRFP requires adherence to Attachment 2 which includes specifications of LAPTOP as set forth in Attachment 2, Appendix A, “A20 – Panasonic Laptop Computer”. Isn’t the government in fact attempting to unduly restrict competition for the LAPTOP in the final RFP? Also, specifications such a 4 USB ports would appear not to be based on TACLAN usage but instead on attempting to limit competition. Please describe the usage case for 4 concurrent USB devices as described in the current TACLAN Baseline?

We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

67.
RFP, SF33, Block 9, Page 1
Provision 52.214-7 listed in this Block is not included in Section L. Please either include provision 52.214-7 in Section L or eliminate it from Block 9.
This has been corrected/changed.
68.
RFP, CLIN 0003, Page 3
C2 Suite is not defined in PWS and Attachments 1 through 6. Please define in PWS and Attachments 1 through 6.
A C2 suite consists of a NIPR and SIPR segment. A full suite consists of a NIPR, SIPR and JWICS segment.
69.
RFP, CLIN 0014, Page 11
Stepladder pricing Item No. = 0026. Please change to 0014.
This has been corrected/changed.
70.
RFP, CLIN 0016 and CLIN 0017, Page 12
Max Quantity = 25, Unit = Lot. Is this for three years, equally distributed over three years, or some other distribution? Please specify locations and frequency at each location.

PWS paragraph 16.0 specifies “like NET”, and NET maximum students is 12. Please confirm 12 as the maximum number of students for Sustainment Training.

This will be defined in the FRFP.

71.
RFP, CLIN 0023, Page 15
Max Quantity = 25, Unit = Lot. Is this for three years, equally distributed over three years, or some other distribution?

Please specify TACLAN user locations, that is, garrison and/or deployed, and the frequency at each location.

Is CBT acceptable for TACLAN user locations?

Please specify the course distribution between commercial sites and TACLAN user locations. Please specify the number of students in a class.

Commercial training has been deleted from the requirement.

72.
RFP, Section L-1.1, Page 60
CLINs state that Full Suites, C2 Suites, and FCDs must be delivered per Attachments 1 – 6 and PWS. Attachments 1 – 6 define the legacy TACLAN systems. The PWS states that the TACLAN Family of Systems must be delivered in accordance with the TACLAN System Specification. The legacy systems are not compliant with the TACLAN System Specification. Similarly, C-LAN kits, MPKs, ROIPs and FMVs are to be provided in accordance with Attachments 7 – 10 and the TACLAN System Specification. The systems specified in Attachments 7 – 10 are not compliant with the TACLAN System Specification. This RFP section states that no deviations from the current approved baseline and equipment list are permitted. Please resolve the conflicting direction.
The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.
73.
RFP, Section L-2.1, Page 60
No font and point size minimums are specified for tables, spreadsheets, graphics, and similar pictorial items. Please provide these format specifications.
Font size shall be uncompressed Times New Roman, no smaller than 8 point for text spreadsheets, tables, and graphics.

One and one-half spaced with at least one inch margins on all sides. Single Spacing for text in tables when tables are not predominantly text.

74.
RFP, Section L-2.1, Page 60
Do foldouts that are predominantly drawings or graphics (ref. L-2.2) count against the page limitation? Please clarify.
No
75.
RFP, Section L-2.1, Page 60
“Offeror provided specification sheets, copies of test plans, test procedures, and test results of previously conducted testing of similar systems using the proposed TACLAN components.” The most credible results of this testing will come from executing the actual TACLAN baseline software which is available only to offerors who already have an authorized copy. Please make the TACLAN baseline software available to all offerors.
The TACLAN baseline software will not be provided during the RFP period.

Section 2.2 states that if the offeror has any test data from similar projects to submit them and they won’t be counted against the offeror’s page limitation.

76.
RFP, Section L-2.2, Page 60
“Past Performance questionnaires received from sources other than the offeror”

Is the government receiving directly from other sources? Is this phrase for information only to the offeror?

The Government reserves the right to receive data from all sources.

77.
RFP, Section L-2.2, Page 60
“Pages that are predominantly drawings or graphics will not be counted against the page limitation.” Please clarify what “predominantly” means here (e.g., greater than 50% of page area?). Also, please clarify what is included in “drawings and graphics” (e.g., such items as organization structures, Gantt charts, tables, spreadsheets, and etcetera?).
Predominantly means 3/4 of the page.

The items mentioned would count as drawing and graphics.

78.
RFP, Section L-3.2.1.1.2, Page 61
PWS section 6.1 does not appear to relate to this proposal section, and PWS Section 9.8 does not exist. Please provide correct references.
This will be corrected in the FRFP.
79.
RFP, Section L-3.2.1.2.2, Page 62
PWS section 9.13 does not exist. Please provide correct reference.
This will be corrected in the FRFP.
80.
RFP, Section L-3.3 Volume II, Past Performance Information Sheets, Page 63
Numbers 9 and 11 appear to be duplicates of numbers 7 and 8. Please remove duplication.
This will be corrected in the FRFP.
81.
RFP, Section L-3.3, Page 63
“L-3.3 Volume III – PRICE” duplicates section reference with “L-3.3 Volume II – PAST PERFORMANCE”. Please renumber Volume III.
This will be corrected in the FRFP.
82.
RFP, Section L-3.3 Volume III, L-3.4.2, IV-A, Page 63
Recommend that the government provide as GFE a limited quantity of the following for test systems: full suites, C2 suites, MPK, FMV, C-LAN, ROIP configurations.
The Government will provide GFE to the successful offeror.
83.
RFP, Section L-3.4.2 / Part IV-C : T&M CLIN’s, Page 63
An Attachment entitled Time and Material Labor Rates is referenced. Will this attachment be provided with the “Attachment 15 Total Evaluated Price Matrix (TEP)” released with the Final RFP (reference section J, page 45) or will this be a standalone attachment? If so, please provide with the Final RFP.
It will be provided in the FRFP.
84.
RFP, Section L-4.3, Page 64
Are the Section L-4.4 items to be included as scanned images on the CD-ROMs? Please clarify.
Yes
85.
RFP, Section L-5, Page 64
Does the government propose any specific discipline/skill breakdown of the 13 TS/SCI personnel? If so, please provide.
The contractor shall describe how they will meet this requirement, The requirement no longer uses 13 as a minimum or maximum number.
86.
RFP, Section M-3.3 Area III : Price / 3rd bullet, Page 71
The CPFF CLIN evaluation description bullet is subordinate to Travel Cost CLIN bullet. Please out-dent and bulletize to have the CPFF CLIN as a standalone bullet.

The statement, “This cost plus the offerors proposed fixed fee percentage contained in clause H1 multiplied by this cost will be used to calculate each Offeror’s estimated cost for System Engineering Support.” is repeated. Please remove duplication.

All have been corrected.

87.
RFP, Section M-3.3, ALL FFP CLINs, Page 71
“times 12” implies that the CLINs are delivered on a monthly basis. Does this mean that CLINs 0016, 0017, and 0023 will be delivered at up to 25 times in each month? Similarly, does this mean that the Provisioning CLIN 0022 will be delivered each month? Please provide clarification.
This has been corrected in the FRFP.
88.
RFP, Section M-1.3, Page 69
Since there are more than 10 attachments, please specify which 10 comprise the current approved baseline.
The baseline is comprised of Attachments 1 thru 10. Also, there is a new attachment included, Attachment 19.
89.
RFP, Section M-1.3, Page 69
The PWS references the TACLAN System Specification. Which TACLAN version (v10.0, v10.1, v10.2, or v10.3) is the current approved baseline that matches to the TACLAN System Specification in Attachment 13? Please clarify.
There are no current baselines that align directly with the TSS.

The TSS has been removed as a core document for this requirement. We are requesting bidder’s propose on baseline 10.1 using Attachments 1 thru 6 and 19.

90.
PWS, Section 3.3, Page 8
Attachment 7 documents only the C-LAN legacy hardware. Other attachments provide ROIP, MPK, FMV legacy information. Please provide similar attachments for Full Suites and C2 Suites in order to fully specify all the legacy systems.
All documentation is in the Bidder’s Library.
91.
PWS, Section 7.1 and 7.1.x, Pages 15 and 16
Is the government’s intent to have the offeror perform LRIP development coincident with legacy transition? Please clarify.
Yes
92.
PWS, Section 7.2, Page 16
Will the LRIP include only the current baseline software or some other major or minor software release? Please provide clarification and specification.
It will include the new 10.1 baseline. The differences have been listed in Attachment 19.
93.
PWS, Section 8.5, Page 19
“full set of COTS manuals” needs further specification. This could be interpreted to range from the documentation that comes in the shipping box, that is, the paper or CD-ROM materials, to the Intel microprocessor technical manuals for the server processor. Please provide clarification and specification.
This requirement has been removed.
94.
PWS, Section 11.1, paragraph 2, Page 32
Second paragraph in 11.1 states “The TACLAN Contractor shall respond to intrusion detection system alerts to verify device(s) compromised and review, analyze, and resolve events.” This seems to imply that TACLAN contractor personnel will be actively monitoring the network. Is it the Government’s intent to have the Contractor(s) provide real-time monitoring support to the J6 IA team? Please clarify.
This requirement has been removed.
95.
PWS, Section 11.1, paragraph 6, Page 33
Please define and clarify what is meant by “the level of acceptance defined by DoD and NSA standards”. What are the specific standards? And is there a specific reference for the “acceptable” level? Please specify.
This requirement has been removed.
96.
PWS, Section 12.2.1, second paragraph on page, Page 38
Do fault decision trees exist to support initial diagnosis and identification of TACLAN-related incidents for legacy systems? Are solutions to resolved incidents for legacy systems documented in a central knowledgebase? If so, please provide.
All available documents will be provided during the transition period.
97.
PWS, Section 16.0, Page 40
Does a legacy Sustainment Training Plan exist? If so, please provide.
Yes
98.
PWS, Section 18.0, Page 41
Section J does not have an attachment entitled, “Exit Plan Elements.” Please provide the attachment.

This is the start of the file's text. The full file is on GovTribe.

Other files

File Type Posted
Attachment_20_TACLAN_TEP_Matrix_Final 21 Jun .xls XLS spreadsheet
Attachment 7 C-LAN.pdf PDF
Amendment 6.pdf PDF
Attachments 7 8 9 19 21.xlsx XLSX spreadsheet
Attachment_20_TACLAN_TEP_Matrix Final.xls XLS spreadsheet
Amendment 5.pdf PDF
Final RFPH92222-11-R-0010 Questions2.pdf PDF
Attachment_20_TACLAN_TEP_Matrix Final.xls XLS spreadsheet
Exhibit A TACLAN CDRL LIST.pdf PDF
Attachment 12 TACLAN SOW Final.pdf PDF
Attachment 16 TACLAN_Performance_Measurement__Oct 4 10_ v7x.pdf PDF
Attachment_20_TACLAN_TEP_Matrix Final.xls XLS spreadsheet
Amendment 4.pdf PDF
Attachment 17 TACLAN Labor Categories.pdf PDF
Attachment 10 ROIP.pdf PDF
Amendment 3.pdf PDF
Attachment 13 TSSx.pdf PDF
Attachment 11 Legacy Suites.pdf PDF
Final RFPH92222-11-R-0010 Questions.pdf PDF
Final RFPH92222-11-R-0010 Questions.pdf PDF
Attachment 10 ROIP 23 May 2011.pdf PDF
Amendment 0002.pdf PDF
Attachment 7 CLAN 23 May 2011.pdf PDF
Attachment 8 FMV 23 May 2011.pdf PDF
Attachment 19 Full Suite C2 Suite NIPR SIPR JWICS 23 May 2011.pdf PDF
Attachment 9 MPK 23 May 2011.pdf PDF
Amendment 0001.pdf PDF
Attachment 21 FCD 23 May 2011x.pdf PDF
TACLAN Brand Name J A.pdf PDF
Exhibit A TACLAN CDRL LIST.pdf PDF
Attachment 17 Labor Categories.pdf PDF
Attachment 14 TACLAN DD 254.pdf PDF
Attachment 16 TACLAN_Performance_Measurement.pdf PDF
Attachment 15 - Exit Plan Elements.pdf PDF
Attachment 18 GFE.pdf PDF
Attachment 6 v10 1 SPS.pdf PDF
Attachment 2 v10.1_O M_Manual.pdf PDF
Attachment 19 v10.1 Full Suite Hardware 12 Apr 2011.pdf PDF
Attachment 1 v10 1 VDD.pdf PDF
Attachment 3 v10 1 Install Manual.pdf PDF
Attachment 5 SRS v10.1.pdf PDF
Attachment 12 TACLAN SOW Final.pdf PDF
Attachment 20 TACLAN_TEP_Matrix.xls XLS spreadsheet
Attachment 4 v10_1_SAG.pdf PDF
Final TACLAN RFP 5 May.pdf PDF
TACLAN PRE-SOLICITATION SIGN UPx.pdf PDF
TACLAN Pre-SolicitationDay 20110330 Finalx.pdf PDF
ECA_instructions__final_x.pdf PDF
TACLAN Draft RFP _Q and A_- for posting 17 Feb 11x.pdf PDF
Attachment 6 SPS.pdf PDF
Show 40 more

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

On GovTribe

Work with this file

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

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