JSDR Development Questions and Answers Complete.xls

XLS spreadsheet 1 MB Posted Aug 14, 2012

Attached to: Joint Spectrum Data Repository (JSDR) Development
Solicitation number: HC1047-12-R-4031
Issued by: Defense Information Systems Agency

View the file

Other files

File	Type	Posted
HC1047-12-R-4031-0004.pdf	PDF	Aug 30, 2012
HC1047-12-R-4031-0003.pdf	PDF	Aug 23, 2012
HC1047-12-R-4031-0002 FINAL.pdf	PDF	Aug 14, 2012
JSDR Development Questions and Answers.xls	XLS spreadsheet	Aug 8, 2012
HC1047-12-R-4031-0001.pdf	PDF	Aug 8, 2012
HC1047-12-R-4031.pdf	PDF	Aug 1, 2012
Attachment 2 - Past Performance References.docx	DOCX document	Aug 1, 2012
Attachment 4 - Form DD254.pdf	PDF	Aug 1, 2012
Attachment 1 -Past Performance Cover Letter and Questionnaire.docx	DOCX document	Aug 1, 2012
Attachment 3 - Cost-Price_Worksheet_Template.xlsx	XLSX spreadsheet	Aug 1, 2012

On GovTribe

Work with this file

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Sheet1

Question	Section/Reference	Statement	Question/Comment	Government Response
1	Section L, Paragraph 4.2 Relevant Contracts	Section L, 4.2 Relevant Contracts states "A contract is considered recent if performed within the last three (3) years"; however Section M, 2.3.2.1 Recency Assessment states "To be recent, the effort must be ongoing or must have been performed during the past five (5) years".	Can the government please update Section L, 4.2 Relevant Contracts, to five (5) years for consistency with Section M, 2.3.2.1 Recency Assessment?	Section L, 4.2 is revised to five (5) years to be consistent with Section M. Please see solicitation amendment.
2	Section L, Paragraph 6.3.3 Associate Contractor Agreements	Include Associate Contractor Agreements, if applicable	Please clarify the requirement to “Include Associate Contractor Agreements, if applicable”? Is it referring to FAR Section 5352.217-9500: Associate Contractor Agreements, which is specifically applicable to the Air Force Space and Missile Center Activities (FAR Supplement 53)? If ACAs are not envisioned, then there is no requirement to provide anything to meet section 6.3.3, correct?	Yes, that is correct.
3	Section B - Supplies or Services and Prices, ITEM NO 1007, Option ABAC Development		ITEM NO 1007, Option for ABAC Development, is identified as FFP; the other ABAC Development Options are listed as CPFF. Does the government intend for ITEM 1007 Option ABAC Development to be FFP or CPFF?	ITEM 1007 is intended to be CPFF.
4	Section L Paragraph 1.2.1.1		Do 11 x 17” pages with information printed on a single side count as two pages?	No, but 11 x 17" pages is only acceptable for foldouts. See Section L, Paragraph 1.2.1.1 Page and Size Format
5	Section M	Sub-Factor 1: Technical Approach A -The contractor shall demonstrate and describe an understanding and working knowledge of Oracle 11g database maintenance activities and configuration control management best practices, and shall have designed and implemented embedded database test services and have experience importing different schemas and meta-data into an existing Oracle 11g database. -The shall describe and demonstrate how they implemented data updates in a web environment, implemented DoD information assurance policies and regulations, and deployed and maintained applications particularly in an Enterprise Service Center (ESC).	In the text from the RFP is the term Enterprise Service Center (ESC) referring to a DECC?	Yes. The term "DECC" was recently replaced by the term "Enterprise Service Center (ESC)". The DISA ESC (DECC) that will house DSO production systems is located in Oklahoma City.
6			Would the government consider moving the Table of Contents to Volume II Technical/Management Proposal?	No.
7			When the Government states that Table of Contents is for the whole proposal which volumes are being referred to specifically (e.g. does that include Pricing Proposal)?	The following sections describe the Tables of Contents expected in the proposal:

1.2.1 Each page shall be counted except the following: cover page, Volume Table of Contents, List of Tables and Drawings, Glossary of Terms and Acronyms, Resumes and Cross-reference Matrix.

1.2.4 Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.2 Include a master table of contents of the entire proposal.

3.2.2 The Technical/Management volume shall be organized according to the following general outline Table of Contents

(1) List of Table and Drawings

(2) Glossary

(3) Cross Reference Matrix

(4) Subfactor 1a: Technical Approach

(5) Subfactor 2b: Management Approach

(6) Risk, addressed for each subfactor

(7) Work Breakdown Structure (WBS). Provide a WBS to level 3 for each Subfactor

5.2 The Cost/Price volume shall consist of the following sections:

SECTION 1 - Table of Contents;

8	Would the Government consider combining the Executive Summary 5 pages with the Technical/management proposal and making that Volume I?	No
9	Would the government consider a 10 day extension to the current due date?	No
10	Would the government consider expanding the Technical/Management Volume to 50 pages?	No
11	What is the minimum percentage of work required by the Prime? Is it 50 percent or less?	The minimum percentage of work required by the prime is 50 percent.
12	Does the JSDR contract have a requirement that the Small Business Prime contractor identify Key Personnel in the RFP proposal?	Yes, all key personnel required to implement the proposed technical solutions must be identified.
13	The Small Business Prime Contractor is required to have 5 past performances, would the proposal be considered non - compliant if the sub -contractors have less than 5 past performances?	The proposal may still be considered, but the risk associated with a lack of past performance may negatively impact the evaluation of the proposal.
14	The RFP did not describe a transition of work from existing contractors, Does the government expect there will be a transition period and should the Small Business Prime Contractor plan for transition in our proposal?	This contract does not duplicate activities currently being performed under any other DSO contract. New capability additions to JDAWS developed under this RFP must be implemented in close coordination with the existing maintenance contractor, who is working under a different contact. Thsi maintenance contractor is responsible for JDAWS availability to DSO customers.
15	Would the government consider expanding allowable past performances to contracts performed within the last 5 years if it is a DISA reference?	The proposal may still be considered, but the risk associated with aged past performance may negatively impact the evaluation of the proposal.
16	Is there a reason why the Government did not define LCATS in the RFP?	DSO will not specify a technical solution. The proposed technical solutions will predicate the labor categories needed by the contractor to accomplish the requested work.
17	Is the Government allowing the Small Business Prime Contractors to define LCATS?	The proposed technical solutions will predicate the labor categories needed by the contractor to accomplish the requested work.
18	Can the Government provide understanding if the current staffing levels are to be augmented via JSDR RFP or completely replaced?	This contract does not duplicate activities currently being performed under any other DSO contract.
19	It is our understand that the Government may not be able to provide onsite space for JSDR work, what are the security requirements for off-site work?	Software/database development task work is expected to be performed at contractor facilities. DSO operates development and test environments at the SIDUS Hosting Facility in Annapolis, Maryland, and at the JITC Test Laboratory at Fort Meade, respectively.

The contractor is expected to perform periodic software deployments via Forge.mil to the development environment for evaluation, informal testing, and demonstration purposes, as needed, or upon request.

Security+ or higher level DoD-acceptable credentials (e.g., CISSP) are required for personnel who perform system administration or tasks that require elevated privileges on DSO servers and IT components at the DISA JITC Laboratory, or at the associated ESC (DECC).

To access the SIPRNet Test environment at the JITC Lab, personnel must annually complete the, "DoD IA Awareness (for DoD Personnel)" training module, located at http://iase.disa.mil/eta.

20 Can the government describe if application server development is a requirement for JSDR and if so, which application server required? The current JDAWS application uses a combination of Java, Javascript, PL/SQL, SQL, and HTML. The back-end database platform for the current JDAWS system is Oracle DBMS 10g (Version 10.2). JDAWS utilizes Apache and Oracle Glassfish for its HTTP Web and Java application servers, respectively. Although these technologies are currently being used in JDAWS, DSO does not mandate a particular set of technologies in this RFP.

The contractor is expected to add the referenced addtitional JDAWS functionality in close coordination with the current JDAWS maintenance contractor, who will work under a different contract. This maintenance contractor has overall responsibility for the availability of JDAWS to our customers.

The primary focus of this software development RFP is to develop a suitable modern replacement for the JDAWS application and its associated database. The JDAWS replacement shall be produced using modern software/database development tools, languages, and techniques that comply with DoD IA policies. The current legacy system may serve as a point of reference for the modernized JSDR development.

Again, DSO does not mandate a particular set of technologies to be used for the software development for this RFP. The contractor should be flexible, however, with regard to technology knowledge and implementation, since the JSDR system will be linked to other DSO/JSC programs, such as GEMSIS.

21		Does the government have an estimate in mind for the LOE or number of personnel it would take to complete the tasks?	The contractor should specify those individuals it believes are key to their proposed solution. DSO will not mandate or designate a list of key personnel on this contract. The LOE or number of personnel required to complete the tasks is dependent on the contractor's approach to development of the JSDR systems within the specified time period.
22	Page 112: 52.237-9000 Key Personnel	Page 112 of the PWS talks about Key Personnel, but there are no labor categories listed in the table. Is it the Government’s intent to provide a list of desired key personnel, or should the contractor specify those it believes to be key to their proposed solution?	The contractor should specify those individuals it believes are key to their proposed solution. DSO will not designate a list of key personnel on this contract. Such a list is dependent on each contractor's approach to development of the JSDR system within the specified time period.
23	Page 95	Figure B-2. JSDR Test Environment figure is missing.	Figure is provided on the "JSDR Test Environment" sheet of this spreadsheet file. The JSDR test environment is currently maintained at the JITC Test Laboratory, located at DISA Headquarters in Fort Meade, Maryland.
24	Page 93	Figure B-1. JSDR Development figure is missing	Figure is provided on the "JSDR Development Environment" sheet of this spreadsheet file. The JSDR development environment is currently maintained at the SIDUS Hosting Facility located in Annapolis, Maryland.
25	Page 76, Section 8. Place of Performance	Section 8 of the RFP (Place of Performance) states that “All work related aspects of this PWS shall be performed at the Joint Spectrum Center in Annapolis, MD, the contractor facilities, or the JITC Test Lab, Ft. Meade, MD. Is it the Government’s intent to have this work done at contractor site with frequent visits to the Joint Spectrum Center in Annapolis and the JITC test lab at Ft Meade for meetings, etc?	Software/database development task work is expected to be performed at contractor facilities. DSO operates development and test environments at the SIDUS Hosting Facility in Annapolis, Maryland, and at the JITC Test Laboratory at Fort Meade, respectively.

Whenever possible, routine meetings should be held via teleconference and/or e-collaboration. JITC Test Lab visits are required only as necessary to support development activities, as determined by the contractor.

26 Page 76, Section 8. Place of Performance Section 8 of the RFP also states that “any equipment such as laptops or phones provided to contractor personnel shall be returned at the termination of the engagement…”. Does the Government intent to provide equipment (laptops, etc) to perform this work to every contractor personnel supporting this effort? This is a generic contractual statement. Distribution of laptops (or phones) to contract personnel are not anticipated, but may be procured and provided on an as-needed basis. Software and database development activities cannot be performed on government computers connected to the NIPRNET.

Software and database development activities are expected to be performed on contractor laptops and/or workstations, via VPN connections to DSO's software development environment at the SIDUS Hosting Facility in Annapolis, Maryland.

27 Page 116, section b) The RFP mentions 8570.1 Security+ requirements. Is it the Government’s intent to require everyone on the contract to have a Security+ certification prior to starting work? Or will time be given to obtain these upon award? Typically 8570.1 requirements are only applicable to personnel having access to server administration. Will developers/analysts/pm be exempt from this requirement? Security+ is only required for personnel who perform system administration or tasks that require elevated privileges on DoD information systems. Personnel will not be permitted to perform system administration or elevated privilege tasks on DSO servers and IT components at the DISA JITC Laboratory, or applicable DECC infrastructure, unless they have Security+ or higher level DoD-acceptable credentials (e.g., CISSP).

Developers, analysts, project managers, and other program personnel will not need to comply with DoDD 8570.1 requirements unless they require “privileged access” to DoD systems, however, to access the SIPRNet Test environment at the JITC Lab, personnel must annually complete the, "DoD IA Awareness (for DoD Personnel)" training module, located at http://iase.disa.mil/eta.

28 Page 9 CLIN 1002 JDAWS Maintenance and Extensions references PWS section 6.12 which describes JSDR Database Maintenance and Extensions requirements. However, PWS section 6.13 describes JDAWS Maintenance and Extensions. Shouldn’t CLIN 1002 reference PWS section 6.13 instead of 6.12? CLIN 1001 should reference "Task 12 JSDR Database Maintenance and Extensions (Option Year 1)", section 6.12 of PWS.

CLIN 1002 should reference"JDAWS Maintenance and Extensions (Option Year 1)", section 6.13 of PWS.

29 Page 16 CLIN 2005 Federated Data Source Integration references PWS Section 6.5 which is titled “Federated Data Source Integration and Maintenance (Base Year)”. Shouldn’t CLIN 2005 reference PWS section 6.28 titled “Federated Data Source Integration and Maintenance (Option Year 2)”? CLIN 2005 should state:

"TASK 5: In accordance with the Performance Work Statement (PWS) Paragraph 6.28, the contractor shall explore federated data options, limitation, and performance."

30	Page 36	In section 5 of the RFP (Scope) the Government describes the required tasks for the contract in all years. Each year (base and options) include Program Management. However, past Option year 1 the Government does not include a CLIN for Program Management. Is it the Government’s intent to exclude costs in the price proposals for a PM function in Option year 2 and 3 and beyond?	For the response, please see CLIN 2013 for Program Management in Option Year 2, and CLIN 3016 for Option Year 3. These CLINs may change when the contract is awarded.
31	Page 37	Table 6.1 of the RFP depicts a High Level Task Overview. It shows tasks numbered 1 – 50 for the the base year and the option years. However, tt appears that there are CLINS (4001 – 4014) that seem to go past option year 3. Is it the Government’s intent to have this contract continue for 6 months past option year 3? In that case is this really a 1 year base and 3.5 options?	It is not the Government's intent to have this contract continue for six(6) months past option year 3. CLINS 4001-4014 are optional CLINs pursuant to FAR 52.217-8.
32	Page 144, 3.2.2 Volume Organization	Section L 3.2.2 of the RFP requests that a Work Breakdown Structure (WBS) be provided to the 3rd level for each subfactor. Which subfactor(s) should be included? Tasks 6.01 – 6.50 and their subfactors?	Tasks 6.01 – 6.50 and their subfactors should be included, plus any subfactors predicated by the proposed technical solution.
33	Page 21 - 34	There is no task for JDAWS support in option year 3. Is it the Government’s intent to eliminate support for JDAWS in OY3?	Yes. It is expected that the Universal Query (Tasks 4, 15, 27 and 39) will replace JDAWS in Option Year 2. A primary focus of this contract is to develop a suitable modern replacement for the current JDAWS application and its associated database. The current JDAWS system will be phased out once the replacement application has been fully developed, tested, and deployed.
34	Page 41	RFP Section 6.2 mentions JDAWS query forms and report options. What are the technologies that are currently utilized for JDAWS query forms and reports? Are you using Oracle Reports? What is the persistence engine used for JDAWS?	JDAWS uses HTML, Java, JavaScript and PL/SQL technologies. JDAWS COTS software currently in use include: Oracle Database 10g (v10.2), Oracle Fusion Middleware 11g, Oracle Glassfish Server (OGS) v3.1, Java JDK v6 update 32, DKO SSO SiteMinder client, and Apache 2.0.64. Although these technologies are currently being used in JDAWS, DSO does not mandate a particular set of technologies in this RFP.

35	Page 42 and 43	Section 6.3.2 “Develop Fixed/Mobile Data Quality Assessment” describes previous work done under the Spectrum Management Transition Initiative (SMTI) Fixed/Mobile logic effort. What is the level of work that has been done? What was produced?	Three sophisticated statistical approaches were explored to produce a relative quality factor, based on a sample population. The different approaches produced varying degrees of confidence, with the primary tradeoff being processing time. This involved a single data element that is dependent on three other data elements.
36	Page 150, 2.3 Technical/ Management Factor	Section M, 2.3 mentions web technologies. Does the Government have a preferred semantic web solution?	At present there is no DoD/DISA-preferred semantic web solution. The contractor is expected to work with DSO technical analysts to determine an appropriate solution for the new JSDR system.
37	Page 39, Section 6.1.1.3	Where is the current legacy software running? Is it deployed at the DISA DECC in OKC?	The current legacy software is running on production servers at the JSC/DSO facility in Annapolis, Maryland. The legacy software is currently being transitioned to the DISA DECC (ESC) in OKC. This is expected to be completed by October 2012.
38

Sheet2

Sheet3

File details come from the government source that posted it. Updated Nov 14, 2017.