MDDC Draft RFP Q & A
| # |
| MDDC Draft Solicitation Questions |
| Answers |
TECHNICAL QUESTIONS
| 1 |
| Is the Offeror responsible for procurement of new and/or replacement products? |
| Yes, under the Materials Contract Line Item Number (CLIN) of the contract. |
| 2 |
| Are there any hardware/software or other equipment components owned by the incumbent contractor which will need to be acquired by the new contractor? |
| The Prime is responsible for managing all Government Furnished Equipment (GFE) on the contract. All GFE will transfer from the current contract to the new contract. |
| 3 |
| An analysis of the IT hardware would imply that some of the servers may be configured as a “private cloud”. If a private cloud is in use, what hypervisor, and Cloud software is being used? |
| No private cloud software is in use at this time. We employ VMWare’s ESX server and View workstation software for virtualization. |
| 4 |
| Are all staff assigned to this contract located at Huntsville and travel to remote sites on a TDY basis, or are some individuals permanently located at remote sites? |
| MDDC Lab Infrastructure and Test and Evaluation Data Acquisition and Communications (TEDAC) personnel are permanently located at remote sites for the Missile Defense Integration and Operations Center (MDIOC) in Colorado Springs, CO and Vandenberg Air Force Base (VAFB) which are at on-site rates. |
| 5 |
| Will the Government provide any workload indicator data (current and/or planned) to assist in developing a staffing solution? |
| No, this information is to be proposed. The offeror is to evaluate the SOW and information in the Bidder’s Library and propose this information. |
| 6 |
| Can MDDC provide any information on the current organizational structure and interfaces within MDDC, MDA and other agencies? |
| Reference Industry Day charts 35 and 37 located on FedBizOpps.gov. |
| 7 |
| What major initiatives or innovations are in the process of being implemented such that they will be completed by the time of contract award? And are there any initiatives or innovations underway that will be the responsibility of the new contractor to complete? |
| None. There are not currently any initiatives or innovations underway that will be the responsibility of the winning offeror to complete. |
| 8 |
| Will the government provide a current master listing of test events that are scheduled to be supported over the next year (i.e., Integrated Master Test Plan)? |
| Integrated Master Test Plan (IMTP) Smartbook has been added to the Bidder’s Library (BL). When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL. |
| 9 |
| Based on the review of DRFP, the COOP/ DR sites appear to be located at Arnold AFB and Corona, CA. Please confirm the COOP/DR sites, whether they are cold or hot, and if any of these sites going to change? If so, where are the new sites planned? |
| Arnold AFB, TN is the MDDC Continuity of Operations/Disaster Recovery (COOP/DR) location (also used to store backup tapes). We are currently working to migrate this site to the Missile Defense Integration and Operations Center (MDIOC) located at Schriever AFB in Colorado Springs, CO during FY12. |
| 10 |
| Does a Help Desk management system exist and if so, what is it? Is the winning contractor required to use it? |
| Currently, the MDDC utilizes Sunview’s Changegear helpdesk software. The winning offeror will need to provide evidence of significant cost savings and process improvements to warrant effort to migrate this activity to another package. |
| 11 |
| Does a Work Order management system exist and if so, what is it? Is the winning contractor required to use it? |
| No. |
| 12 |
| Does a TO management system exist and if so, what is it? Is the winning contractor required to use it? |
| There is no current mandated Government Task Order (TO) management system. The Government encourages offerors to propose innovative management solutions with regard to TO management controls. |
| 13 |
| Does an enterprise server management system exist and if so, what is it? Is the winning contractor required to use it? |
| The MDDC uses Microsoft System Management Server (SMS) for application level services. We currently use Intermapper for hardware and connectivity monitoring. The winning bidder would need to provide evidence of significant cost savings and process improvements to warrant effort to migrate this activity to another package. |
| 14 |
| Will MDDC consider or allow an introduction to the past performance volume in order to introduce the team and summarize capabilities and experience for the reviewers? |
| Past and Present Performance volume page limit has been revised to “N/A”. |
| 15 |
| Given that many MDDC requirements necessitate niche corporate experience and teaming arrangements, would the Government be willing to consider changing the past performance requirement from a minimum of 3 to “up to 3” PPIS for subcontractors performing a niche or highly specialized companies that may be small but still meet the critical/key standard? |
| No. Past and Present Performance Information Sheets may be submitted on either Government or commercial contracts (see L-7.2). |
| 16 |
| Will the staff be required to: “prepare, maintain, and submit comprehensive reports detailing all MDDC activities (i.e., CDRL A001, CDRL A004, CDRL A006, CDRL A007, CDRL A021)”; “manage program cost, schedule, performance, risks, subcontracts, vendors, and data”; “develop, implement and maintain a quality assurance program”; and “provide and execute a procurement system” be directly billable to the contract as part of issued Task Orders? Or does the government expect these personnel resources to be included in the bidder’s indirect rates? |
| Yes, the contractor staff will be required to prepare, maintain, and submit comprehensive reports detailing all MDDC activities. |
| 17 |
| Please clarify why the labor category Level 1, which normally equates to a Junior, is shown with 0-10 years experience? This broad range of experience normally encompasses at least 3 if not 4 levels under standard Federal Contracts. Similarly, industry salary surveys typically only reach levels up to 10-12 years for that same reason. |
| Attachment 3 – Govt Labor Categories will be corrected to show the years of experience for Level I as 0 – 5 years and Level II as 6+ years for the following Government Labor Categories: |
· Disaster Recovery Specialist
· Legacy Data Analyst
· Technical Writer
· Administrative Support
| 18 |
| What is the work experience of the workforce (i.e., percentage of workforce at different experience levels)? |
| The required education and technical requirements are included in Attachment 3 – Govt Labor Categories, of the solicitation. |
| 19 |
| On Page 7 of Attachment 4 under the Program Management labor category the Government asks Offerors to price 4 levels of Program Management. On page 10 of Attachment 4, the table titled “MDDC Program GLC Minimum Qualifications” only lists experience requirements for 3 levels of Program Management. Please clarify whether there are 3 or 4 levels associated with the Program Management labor category? If a 4th level is required, please provide the labor category qualifications? |
| Attachment 3 – Govt Labor Categories, will be corrected to show only 3 levels for the Program Management Government Labor Category (GLC). |
| 20 |
| Since DIACAP is the current standard, are the references to DITSCAP in this paragraph correct? (SOW 4.6.b) |
| No. References to DoD Information Technology Security Certification and Accreditation Process (DITSCAP) are inaccurate. DoD Information Assurance Certification and Accreditation Process (DIACAP) is correct and the Statement of Work (SOW) 4.6.b and CDRL A016 will be changed to reflect this. |
| 21 |
| M-5.2 Technical Subfactor 2 Software. The introductory sentence to the evaluation criteria references Information Technology. Should it state Software? |
| Section M-5.2, Technical Subfactor 2 - Software, will be corrected. “Information Technology” will be deleted and replaced with “Software” in the introductory sentence. |
| 22 |
| GPS data processing and analysis equipment utilization is included in the SOW. Please clarify under which subfactor it will be evaluated. (SOW4.2.1h) |
| Only discriminators are being evaluated. Offeror will be required to address Global Positioning System (GPS) data processing and analysis equipment utilization in their proposal (see paragraph L.3-10). |
| 23 |
| Sustaining and utilizing a test resource deconfliction and planning tool are included in the SOW. Please clarify under which subfactor it will be evaluated. (SOW 4.2.1i) |
| Only discriminators are being evaluated. Offeror will be required to address all SOW requirements in their proposal (see paragraph L.3-10). |
| 24 |
| If a test event fails during the transition period, what is the division of responsibility between the incumbent and new contractor? |
| The incumbent would have lead responsibility for supporting the event and would identify specific tasks the new contractor should support. The New Contractor would be required to “shadow” the incumbent. |
| 25 |
| Please clarify if Statement of Work section 4.3 Data Management was not intended to be included in any Technical Subfactor as a reference SOW section. |
| Only discriminators are being evaluated. Offeror will be required to address all SOW requirements in their proposal (see paragraph L.3-10). |
| 26 |
| In the MDDC Program Government Labor Categories (GLC) Table, Program Management has four (4) levels defined but in the MDDC Program GLC Minimum Qualifications Table, Program Management has three (3) levels defined. Please clarify whether there will be four (4) or three (3) levels of the Program Management GLC? |
| Attachment 3 – Govt Labor Categories, will be corrected to show only 3 levels for the Program Management GLC. |
| 27 |
| Attachment 3 Labor Categories and Qualification lists Program Management with Levels I through IV. However the GLC Minimum Qualifications matrix says N/A for IV. Exhibit C BOE estimate also includes a PM level IV. Does the government intend to provide minimum qualifications for the Level IV PM category? |
| Attachment 3 – Govt Labor Categories, and Exhibits B1, B3, B4 and C will be corrected to show only 3 levels for the Program Management GLC. |
| 28 |
| It does not appear that SOW Sections: Section 3. Mission Assurance, Section 5. Mission Focus, Section 6.Security, Section 7.1 Relocation of Operations are addressed in either Section L or Section M. The assumption is the government would like us to address these sections in our proposal. Does the government intend to provide additional Section L and M guidance on addressed SOW sections? |
| Only discriminators are being evaluated. Contractor will be required to address all SOW requirements in their proposal (see paragraph L.3-10). |
| 29 |
| For any potential work that is anticipated to be performed at contractor site should the rates include contractor site overhead, or does the government wants all rates bid at the government site rate? If there is anticipated contractor site work, does the government have a percentage of work estimates for the potential contractor site work? |
| Off-site rates need to be included for all efforts that reside outside of Government facilities. Offerors should propose innovative approaches or efficiencies to take advantage of available Government facilities to minimize off-site rates. |
| 30 |
| SOW paragraph 6.1.1 a) mentions TS processing requirements. Can the government provide the number of TS billets that will be required to support MDDC operations? |
| No. However, the anticipated maximum is < 30. The expectation is that the offeror will identify the minimum number of Top Secret (TS) cleared personnel to accomplish all tasks under this contract. Work at the TS level is expected to be less than 5% of the effort. Cross training and/or multitasking personnel to execute all contract tasks at the TS level with the minimum number of TS clearances is an example of the efficiencies the Government is looking for in this award. |
| 31 |
| In the DRFP some key SOW elements are not explicitly addressed in Section L or M; (Section 3. Mission Assurance, Section 5. Mission Focus, Section 6.Security, Section 7.1 Relocation of Operations). |
In the final RFP will the Government revise Attachment 13 to clearly identify the cross references between the SOW and Sections L and M?
In the final RFP will the Government revise Section L to explicitly identify where each SOW element should be addressed in the proposal?
In the final RFP will the Government revise Section M to explicitly identify which factor and subfactor each SOW element will be evaluated against?
Section L provides information regarding how to submit proposals. Section M provides details on how proposals will be evaluated. These are discriminators the Government has determined to be critical to successful performance of the contract. However, the contractor will be required to perform the entire scope of work (see paragraph L-3-10).
| 32 |
| Section L-5 provides guidance for six (6) Technical Subfactors. The SOW under paragraph 4 Operations and Sustainment also provides information on 6 major efforts. Four of these topics directly match (IT, Software, Library Operations and Truth Analysis). The remaining two efforts in the SOW are titled: Test Support Systems and Data Management. In Section L they are titled TEDAC and TM Operations. Is it the Government’s intent that these are the same topic areas and that in addressing the Section L guidance all SOW topics are covered? |
| TEDAC and TM Operations are covered under test support. Section L provides information regarding how to submit proposals. Section M provides details on how proposals will be evaluated. These are discriminators the Government has determined to be critical to successful performance of the contract. However, the contractor will be required to perform the entire scope of work. |
| 33 |
| Section L-6.2 Management Subfactor 2 – Management Approach, which states: “5) Offeror shall provide a Contract Work Breakdown Structure (CWBS) and dictionary, which reflects the Offeror’s understanding of the contract effort… The reference document for developing the WBS and dictionary is MIL-HDBK-881A.“ Several questions arise given this requirement: |
Given the potential for additional page count used to address this requirement will the government add pages to the management volume or exempt the CWBS from the page count?
Does the government intend to provide a Program WBS (PWBS) to provide the top level MDDC WBS organization? Should the Offeror use the SOW as the basis or will additional guidance be provided in order for the Offeror to construct the CWBS?
Section L-2.1 has been revised to include Contract Work Breakdown Structure (CWBS) and dictionary as an exception to the page count. No Program WBS (PWBS) will be provided. The offeror can use the SOW as the basis for the CWBS.
| 34 |
| Will the government provide the incumbents phase-out plan? |
| No, a phase-out plan is not available at this time. |
| 35 |
| Can the government provide typical turnaround times for processing data after receipt? |
| The target to turn around ad-hoc data requests and Integrated Data Management Plan (IDMP) requests (upon data receipt) is 48 hours. |
| 36 |
| Can the government provide what software is used for the data repository (i.e. Database, Oracle, etc.)? |
| Internally developed software (the Data Management System) utilizing a Microsoft SQL Server database backend. Data files are stored on the server and not in the database. |
| 37 |
| Can the government provide what other software/platforms are used (i.e., Java, .NET, HTML, Web Services, C++, etc.)? |
| Development toolsets used are: |
Primary toolsets/languages:
C#, CFML, .NET 3 and 4, Other toolsets/languages:
Aspose.Words for .NET, AutoEdit SciTE script editor, CFAJAX, CSS, HTML, IronPython, Javascript, log4net, Lucene .NET, MATLAB, Microsoft C/C++/VB, Microsoft SQL Server Transact-SQL, NHibernate, OpenNETCF Desktop Communication PDF 417 Library, Rimage Rabid API, Teltron Scripting Language, VBScript (Access/Excel)
| 38 |
| Can the government provide if there is an approved list for Open Source Software? |
| There is no approved list for FOSS (Free/Open Source Software). The MDDC Program has developed an internal review process to ensure that any FOSS requested for the Test Data Analysis Network (TDAN) networks are thoroughly reviewed, and justified against any commercially available software. |
| 39 |
| Can the government provide system documentation, ATC, SSP, IP, certification, appointment letters, and audits that are available? |
| Yes, this information is available within the Bidder’s Library (BL). |
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
| 40 |
| Attachment 13 - Cross Reference Compliance Matrix (also referenced in the RFP, Section L-3.8(e)) – has a column for a CWBS element. A WBS is most likely at a Task Order level, given that this is an IDIQ, please provide an example of the type of information that should fill this column. |
| Each CWBS element number/ title that maps to each SOW paragraph is to be entered into the “CWBS” column. |
The CWBS should cover 100% of the work defined by the SOW and capture all the deliverables.
| 41 |
| Section 4.5.1 of the SOW says we shall develop software development plan “commensurate with SEI/CMMI Level 3”. What is the government’s definition of commensurate? Do we have to be officially assessed at CMMI Level 3 by SEI? |
| The Government is looking to drive all software development on the contract to use a common set of processes and procedures. In this sense, the word ‘commensurate’ refers to an equivalency to Software Engineering Institute/Capability Maturity Model Integration (SEI/CMMI) Level 3 processes, procedures and documentation in regards to software development. |
No, the offeror does not have to be officially assessed at CMMI Level 3 by SEI or any other approved assessment provider.
| 42 |
| Section 6.1.4 of the SOW states the contactor shall “employ a sufficient number” of personnel with TOP SECRET clearances. What is a quantitative number of “sufficient” |
| No. However, the anticipated maximum is < 30. The expectation is that the offeror will identify the minimum number of TS cleared personnel to accomplish all tasks under this contract. Work at the TS level is expected to be less than 5% of the effort. Cross training and/or multitasking personnel to execute all contract tasks at the TS level with the minimum number of TS clearances is an example of the efficiencies the Government is looking for in this award. |
| 43 |
| Section l-3.8 requires a 15-page Executive Summary that includes Teaming Arrangements. If the government wants copies of fully executed teaming agreements, can the TAs be excluded from the page count because a single TA is typically a 10 to 15 pages document? |
| Fully executed teaming agreements are not required in the Executive Summary. Include teaming arrangements. |
| 44 |
| Section L-3.5 says the contractor must convey we have “sufficient resources”. What is the definition of a resource in this context? |
| Resources refer to facilities, personnel, equipment, systems, experience, expertise, certifications/ licenses, etc. necessary to execute the SOW requirements. |
| 45 |
| Section L-5.1 (1) requires us to discuss “the recruitment and staffing” of the workforce. Section L-6.2(2) requires us to describe our approach to “personnel recruitment”. These seem like redundant requirements. Should our approach and capabilities for recruitment be limited to the Management Approach, or does the government prefer we discuss recruitment in both sections? |
| Offerors should discuss recruitment in both sections Section L-5.1(1) and Section L-6.2(2). Section L-5.1(1) is specific to personnel who will execute Information Technology operations. Section L-6.2(2) covers all personnel who will execute the entire SOW requirements. |
| 46 |
| Section L-6.1(2) limits the positions descriptions (PD) and qualifications package to 2 pages person. Will the government consider increasing that to 3 pages, since a PD will be approximately 1 page and a qualification package could easily be two pages. |
| Yes, page limitations have been increased from 2 to 3. |
| 47 |
| Section L-6.2(5) requires a CWBS. Will the Government consider excluding this from the page counted sections? |
| Yes, Section L-2.1 has been revised to include CWBS and dictionary as an exception to the page count. |
| 48 |
| Should bidders assume government facilities will be provided for all MDDC personnel? If not, how many MDDC personnel can be housed within government provided facilities? |
| Government facilities will not be available for all MDDC efforts. Currently the Test Support System (TSS) subcontractors reside off-site at their own contractor facilities, but the Government is looking for efficiencies and innovations from the offerors to minimize these footprints. TSS is comprised of TEDAC, Telemetry Operations (TM Ops), and Translated GPS Range System (TGRS). |
There are 270 full time seats and 50 transient work stations within the Von Braun III (VBIII) lab space this contract effort will support. The VBIII lab space is designed to accommodate and support the MDA Test Functional Area not a single directorate so all seats are supported by this contract, not all seats are occupied by MDDC personnel, and no TSS personnel actually sit in the VBIII basement lab space or on site at VBIII. The discrepancy between hours and seats is a result of multiple directorates having personnel sitting within the VBIII lab space.
| 49 |
| Section 4.4 - Truth Analysis - There is no mention of radar analysis in the Truth Analysis section of the SOW. However, radar analysis is specifically mentioned in Section L (L-5.5) under Technical Subfactor 5. Section M (M-5.5) refers back to SOW Section 4.4 and states that radar analysis experience and technical capability will be part of the evaluation by the Government. |
Proposed Solution – Modify paragraph C of SOW Section 4.4 to read: Perform both radar and optical signature analyses with respect to targets, radars, and interceptors.
Attachment 1, Statement of Work (SOW) paragraph 4.4.1 (c), will be corrected to include radar analysis.
| 50 |
| Section 4.2.1.h “Utilize and validate GFE GPS data processing and analysis equipment for flight and ground test events”. Does the ground test support reference imply supporting the power-up testing as in GMD or THAAD launches, or does it refer to actual Ground Test Missions versus Flight Test Missions? |
| This was in error and was not intended to apply to ground test. Section 4.2.1.h will be modified to remove reference to Ground Test (GT) missions. |
| 51 |
| SOW 1.1 - Please confirm that all documents listed in 1.1 Reference Documents will be available in the bidder’s library. |
| Ref A, Ballistic Missile Defense System (BMDS) Test Concept of Operations, 8 APR 2009: Will be included in the next, currently unscheduled release of the Bidder’s Library (BL). |
Ref B, MDA Directive 3002.03, BMDS Test Policy, 21 JUN 2010: Located in the MDA Directives Folder in the BL.
Ref C, MDA Integrated Master Test Plan, v11.1, 23 FEB 2011: Is not/will not be included. The most current IMTP Smart Book was distributed to all parties who requested the BL documents on 28 Sep 11.
Ref D, MDA Directive 3200.06, Mission-Related Scientific and Technical Data/Information Management, 13 JUN 2008: Located in the MDA Directives Folder in the BL.
Ref E, Pacific Range Support Team Memorandum of Agreement, 04 NOV 2010: Will be included in the next, currently unscheduled release of the BL.
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
| 52 |
| SOW 4.3 - In terms of technologies, what are the required skill sets for Data Management team members? |
| The required technical education and skills are provided in Attachment 3 – Govt Labor Categories of the solicitation provided on FedBizOpps.gov. |
| 53 |
| Will you please provide the number of staff in each current labor category referenced in Attachment 3, Government Labor Categories? |
| No, this information is to be proposed. The offeror is to evaluate the SOW and information in the Bidder’s Library and propose this information. |
| 54 |
| SOW 4.5 - Please list the number of people, their positions and job descriptions who are maintaining these applications today |
| No, this information is to be proposed. The offeror is to evaluate the SOW and information in the Bidder’s Library and propose this information. |
| 55 |
| Will you please provide a list of software this program supports? To include software, tools, and databases, data management software, test analysis software, situational awareness and real-time data transfer software, test resource planning and conflict/resolution software, and telemetry analysis software. |
| This information has been provided in the following: 1) Industry Day brief located on FedBizOpps.gov; 2) Bidder’s Library (BL) documentation; and 3) question 37, above. |
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
| 56 |
| Exhibit_C_- MDDC BOE Summary - The requirements in the Statement of Work (SOW) are generally specified as rather broad task areas, with few details on the scope, complexity, frequency and other parameters that are needed to provide accurate estimates of the level of effort required to satisfy the requirements. This will likely lead to inconsistent estimates for different Contractors, and will also create difficulties for Government evaluations of Prices. |
Question: Will the Government please provide additional details on the task areas so that Contractors have a more well-defined basis for estimating content and frequency of specific task activities? One relatively straightforward way to provide some increase in consistency across proposals would be to revise Exhibit C to specify total hours by Task Area (Program Management, Quality Assurance, ESH, Library Operations, Test Support Systems, Data Management, Truth Analysis, Software Development, Information Technology Infrastructure, Mission Support, Security Operations).
No, this information is to be proposed. The offeror is to evaluate the SOW and information in the Bidder’s Library and propose this information.
| 57 |
| SOW 3.1 - Please provide a list of products and services to be covered under QA. Is the list of products and services to be QA’ed different from the list of product and services to be covered under Software development/maintenance? |
For each of the products/services to be covered under QA, please indicate their deployment environment, their technology stack in which they are developed, and tools used.
Please review the SOW, section 3.1.3.: “After award of the resulting basic contract and issuance of the first Task Order, the Government will coordinate with the contractor during the transition phase to develop an appropriate Quality Assurance Surveillance Plan (QASP) that will be used to monitor the resulting basic contract and task order performance.”
| 58 |
| SOW 3.1 - Please indicate the number and size of applications to be developed/maintained and tested during the base period. Please indicate the expected team sizes, if available, to perform this work. |
| This information is available within the Bidder’s Library (BL). |
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
| 59 |
| SOW 4.5 - For software to be developed, are the requirements developed already or do we need Business Analysts to interview and write the requirements? |
| Requirements development for the software is an ongoing process based on business rule process changes or evolving mission requirements. At this juncture, the development teams manage the development of said requirements. The Government is looking to standardize this process across the program within an economically feasible means. |
| 60 |
| SOW 4.5 - Please provide list of enhancements to make, average number of defects today, average amount of time to resolve these defects. |
| As stated in the answer to question 59, requirements development for the software is an ongoing process based on business rule process changes or evolving mission requirements. The Government is looking to standardize this process across the program within an economically feasible means. |
| 61 |
| SOW 4.5 - Please provide the application requirements/use cases for the applications that need to be maintained under the scope of this work. |
Please provide the high level requirements/use cases (if detailed functional requirements are not done yet) for the applications to be developed under the scope of this work.
The initial high level requirements for the MDDC Data Management System are included within the Bidder’s Library (BL).
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
| 62 |
| SOW 4.5 Based on the industry day slides we understand that the software systems to be developed/maintained are DMS, ASTER and TRMP. Are there any subsystems under these areas or are these actual applications? Are these the only applications to be developed/maintained? The information available in these slides is not sufficient enough to estimate the work involved in these areas. Please describe the requirements, current state of development, the technical architecture and the design of these systems. Please provide any available documentation that will be helpful in estimating the size of these applications. |
| These are the primary applications, along with the software developed for use by the TEDAC and TM Ops groups. There are a number of ancillary applications developed [ref. Bidder’s Library (BL)] for use in support of these primary applications and other MDDC Program activities. Some of these smaller applications require maintenance as needed. Other toolsets may be developed over the course of the contract that support any or all of the MDDC Program activities. Additional technical information is provided in the BL for these applications where this exists (updates will be provided as documentation is made available). The Government is looking for the contractor to standardize MDDC Program software development and documentation processes and procedures. |
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
| 63 |
| SOW 4.5, Software Development - “The contractor shall support the complete lifecycle of BMDS missions and the MDDC Program objectives by developing, delivering, improving and sustaining products for mission planning, mission operations, data collection, data distribution, data transfer, data compression, library operations, communications, telemetry, visualization, truth, metrics, and reporting software products and toolsets.” It is difficult to provide an estimated level of effort for these activities without additional details on the size and scope of these activities. |
Question: Will the Government please provide additional details on the scope of these activities?
The Technical information is contained within the Bidder’s Library (BL).
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
| 64 |
| SOW 3.1 What types of testing is expected for the software products and services? Are there any other types of testing other than the standard Unit testing, Integration testing, System testing, Performance testing and Regression testing. Please provide the types of performance testing that are typically done for these products and services and list the tools utilized. Please indicate the periodicity of these testing activities and the tools used (if any) |
| Due to the structure of the MDDC Program, there is not a standardized Software Development Life Cycle implemented for all software development efforts. Subsequently, there are various states of Quality Assurance (QA)/Testing methodologies implemented for these efforts. The Government is looking for the offeror to standardize MDDC Program software development and documentation processes and procedures. |
| 65 |
| SOW 4.5 - For software development are there any technology or architecture constraints? Examples - technologies, products and tools that cannot be used, MDDC security policies, architecture stipulations that should be met, business principles, architecture principles to adhere to, non-functional requirements/Qualities of Service to be met. |
| Yes. DoD 8500 defines the Information Assurance (IA) parameters for DoD Information Systems (IS). Coding efforts should conform to technologies and practices that are accepted for Government IS and comply with MDA and DoD policies and guidelines. |
The Government is looking to develop and maintain standards of practices for software development across the whole of the MDDC Program.
| 66 |
| SOW 4.0 - Will you please list the internally developed software applications and the programming languages used for each? |
| The Technical information is contained within the Bidder’s Library (BL). |
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
| 67 |
| Will the source code and design documentation for each internally developed application be provided to the new contractor? |
| Yes. Upon contract award all source code within the Government’s possession will be delivered to the new contractor with all supporting documentation. The Transition Plan for both outgoing and incoming contractor shall define how and when this delivery will take place. |
| 68 |
| SOW 2.1.9 - “The contractor shall plan, host, and conduct Program Management Reviews (PMRs), participate in working groups and technical interchange meetings, and conduct planning with the Government and sub-contractors for strategic planning and support for other program activities, as directed.” It is difficult to provide an estimated level of effort for these activities without additional details on the content and frequency of these activities. |
Will the Government please provide additional details on the content and frequency of these activities?
Meeting requirements are driven by the contract requirements, mission and program management. No additional level of effort is required for these activities.
| 69 |
| SOW 2.1.11 - “The contractor shall support the MDDC Program by publicizing and participating in various exhibits, symposiums, and conferences accessible to the MDA Community, as directed.” It is difficult to provide an estimated level of effort for these activities without additional details on the content and frequency of these activities. |
Question: Will the Government please provide additional details on the content and frequency of these activities?
The Government expects to support a minimum of 1 symposium per year with no more than 2 or 3 expected per year. There is no set number in place but direction would be provided to the contractor with sufficient notice to support such an event. Washington DC and Huntsville, AL are the two expected locations where we would expect to support an event.
| 70 |
| Sec. H-33, Program Synchronization - This section requires that the “Contractor shall provide technical data and other information (to include limited and restricted rights data as defined by DFARS 252.227-7013 and 252.227-7014 or information protected under the Freedom of Information Act Exemption 4) to other Ballistic Missile Defense (BMD) Contractors and Government agencies to facilitate MDA objectives.” |
Question: Will the Government please provide guidance regarding the estimated level of effort needed to support this requirement?
The level of effort required to perform the SOW requirements and deliver the CDRL items is sufficient. No additional level of effort is required to perform Program Synchronization requirements.
Exemption 4 applies to matters that are "trade secrets and commercial or financial information obtained from a person and privileged or confidential."
In order to bring a record within this exemption, an agency must show that the information is (A) a trade secret or (B) information that is (1) commercial or financial, (2) obtained from a person, and (3) privileged or confidential.
Information generated by the Government, cannot fall within this exemption.
Requested records will be considered "confidential" within the meaning of this exemption if their disclosure is likely to either impair the Government's ability to obtain necessary information in the future, or cause substantial harm to the competitive position of the person from whom the information was obtained. A pledge of confidentiality from the agency, or the fact that the information at issue is not customarily available to the public, will not qualify requested materials as "confidential" under this exemption.
| 71 |
| SOW 4.5 - What is the distribution today in terms of percentage of people doing software maintenance vs. development? |
| The Government is expecting the offeror to propose a staff of developers to accomplish both software development and maintenance in the most efficient use of personnel resources possible. |
| 72 |
| SOW 3.1.2 - Please provide a listing of any ‘System of metrics’ in use today to track processes that include customer satisfaction, system and program performance, maintenance activities, and problem resolution statistics. |
| The Government will work with the contractor to propose and develop processes and procedures necessary to measure and track all relevant metrics related to the MDDC program. Currently the MDDC Program tracks multiple financial and technical performance measures. Please reference the SOW, section 3.1.3., for additional details. |
| 73 |
| What coordination is necessary among internal and external stakeholders with the planning, documenting, and execution of network communication interfaces between the MDDC Program network infrastructure and other network infrastructures as referenced in SOW 4.6.c? |
| Communication between the MDDC Program and internal and external users/stakeholders in the Information Technology (IT) infrastructure is critical to the success of the MDDC Program. Regular meetings are held with the primary leads for the customer base, as well as Element Points of Contact (POCs), MDA Internal Controls personnel, software development and MDDC Library personnel. Aspects such as customer data growth, personnel changes, IA challenges, new capability requirements, mission requirements, etc. are communicated to the IT infrastructure leads and personnel assigned to work specific tasks on a daily basis. |
| 74 |
| Please clarify the number of facilities and/or location of the facilities referenced in the following statement from SOW 6.1.2. “The contractor shall assist in sustaining the physical security accreditations of all facilities in which the MDDC Program sustains oversight responsibility.” |
| There are 2 accredited collateral open storage facilities located in VBIII. |
· ~50,000 Square Feet
· Multiple Internal Labs
· Common User Areas
· Conference Rooms
· Classified/Unclassified Video Teleconferences (VTCs)
· Transient Work Space
| 75 |
| Please clarify the number information systems are referenced in the following sentence from SOW 6.1.3, The contractor shall operate and sustain multiple unclassified and classified information systems |
| There are five (5) related to the MDDC Program: |
· Unclassified Test Data Analysis Network (UTDAN)
· Classified Test Data Analysis Network (CTDAN)
· Restricted Data Network (RD)
· Mobile Joint Analysis Team Network (MJAT )
· Test Support System (TSS): comprised of TEDAC, TM Ops and TGRS
| 76 |
| Will a base line inventory of the library’s holdings be completed prior to contract award? |
| Yes, the contract and Government currently possess a hand-receipt of all hardware and software items currently on contract. This hand-receipt specifies location, quantity and description of all holdings. All library holdings will be inventoried during transition and transferred to the new prime. |
| 77 |
| How many hard copy items are in the data center? How many electronic files are in the data center’s databases? |
| ~ 102,000 Hard Copy/Physical (all classifications included) |
~ 103,000 Electronic (all classifications included)
| 78 |
| SOW 4.3 - Is there any specific requirement of accepting / preparing data in specific file formats, e.g. EDI |
| Yes - The Integrated Data Management Plan (IDMP) is used to define the data items to be produced during a mission. This document also defines the handling/format details related to the distribution of that item to the data consumer community. Most data transfers are accomplished by either File Transfer Protocol (FTP) or transfer on some electronic media format: Hard disk, DVD, tape, etc. It should be noted that while mission/event data items may be repackaged to some new media format (or possibly converted from hard copy to an electronic format), the data is not changed. |
| 79 |
| What is the renewal date for the Interim Authority to Operate (IATO)? |
| The MJAT Interim Authority to Operations (IATO) renewal is early November. Current TEDAC/TM Ops ATO expires AUG 2012. There are also systems tied to an event IATO/Interim Authority to Test (IATT) supporting AHW/FT-1A that will expire immediately following event support requirements and/or no later than 30 November 2011. TSS does not support TGRS interconnections and they are either accredited by the range or have their own standalone accreditation. TGRS ATO accreditation efforts are underway for MDA owned systems. The TGRS IATO is valid until December 2011, and MDA is aiming for a full ATO by November 2011. TGRS assets located at DoD ranges are either accredited by the range or have their own standalone accreditation. |
| 80 |
| SOW 2.1.7 - Understanding the sensitivity of the data, can the software development and QA activities be performed at the contractor’s facilities or should the software development and QA team be located onsite? |
| The majority of software development and any testing/QA activities are performed at the Government site with the exception of software developed for TSS systems. Note some software updates may occur on-site during mission operations based on last-minute mission requirements. |
| 81 |
| SOW 2.1.7 - For the consultants working onsite, is weekly travel allowed to the onsite facilities from where ever the consultants reside? |
| All travel must comply with the Joint Travel Regulations. |
| 82 |
| SOW 3.1 - Can the bidder suggest their own QA tools? |
| Yes – the contractor may propose using offeror/internally developed QA tools. Note the use of these toolsets must comply with all Government Rights Directives and contract clauses. |
| 83 |
| SOW 4.5 - Please provide the name of the supporting tools and utilities for “key word search” used in DMS |
| This is an internally developed toolset for the specific use by one of the Element groups. It was developed in C# reusing code libraries from the Data Management System code base. |
| 84 |
| SOW 4.5 - Please provide the software development and integration tools, deployment environment, technologies, middleware, databases, and processes currently used. Can the vendor propose any of these tools and technologies of their choice?) |
| Reference the Bidder’s Library (BL). |
As to any changes related to tools and technologies used on the program, the bidder is welcome to propose these. The Government is looking for all manner of efficiencies in regards to software development. However, the bidder would need to provide the Government significant evidence that any proposed changes to highly integrated tools, middleware, etc. would be in the best interest of the Program and not cause significant delays and/or cost to the Program or delivery of software.
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
Refer to the following RFP clauses for requirements regarding Procuring Contracting Officer approval of changes:
H-31TECHNICAL COGNIZANCE
H-37 INSERTION OF LIMITED OR RESTRICTED RIGHTS
| 85 |
| SOW 4.5 - Please list all the COTS/GOTS and open source tools that each of the software applications should integrate with and their purpose of integration. What integrations already exist and what need to be developed in the future? |
| Please reference the Bidder’s Library (BL) and Industry Day brief (brief located on FedBizOpps.gov). Note future requirements for software application development will be based on program and mission requirements as directed at that time. |
When additional information is available, it will be included in an update to the BL. Automatic distribution to all previous requestors will be provided upon updates to the BL.
| 86 |
| SOW 4.5 - What System Development Lifecycle methodology (SDLC) does MDDC follow for software development? Are you open to changing the SDLC to what the vendor suggests? |
| System Development Lifecycle (SDLC) varies from group to group. As stated in the Industry Day brief located on FedBizOpps.gov, the Government is looking to standardize development processes across the whole of the contract. |
Yes, the Government will consider the offeror’s proposed methodologies.
| 87 |
| SOW 6.1.2 - Please provide a list of the facility locations in which the MDDC Program sustains oversight responsibility and the contractor will assist in sustaining the physical security accreditations |
| There are 2 accredited collateral open storage facilities located in VBIII. |
· ~50,000 Square Feet
· Multiple Internal Labs
· Common User Areas
· Conference Rooms
· Classified/Unclassified VTC’s
· Transient Work Space
| 88 |
| Section M does not reference the SOW section 4.3, Data Management, as a focus area. Please note in M-5.x where section 4.3 applies. |
| Only discriminators are being evaluated. Contractor will be required to address all SOW requirements in their proposal (see paragraph L.3-10). |
| 89 |
| SOW 4.6 - Attachment 12 provides a raw listing of every hardware component in the environment. Will a listing by server/workstation be provided that shows how those components constitute actual server/workstation builds. |
| This information is being updated for the next release of the Bidder’s Library (BL). Automatic distribution to all previous requestors will be provided upon updates to the BL. |
| 90 |
| SOW 4.6, Information Technology Infrastructure - “The contractor shall develop, operate, document and sustain integrated Information Technology (IT) Operations, System and Network Management and Administration, IMTP and Test Functional Analysis Lab Operation Management, and Information Assurance (IA) product development for assigned MDDC Program networks and systems as required by the Government.” It is difficult to provide an estimated level of effort for these activities without additional details on the size and scope of these activities. |
Question: Will the Government please provide additional details on the scope of these activities?
No, this information is to be proposed. The offeror is to evaluate the SOW and information in the Bidder’s Library and propose this information.
| 91 |
| SOW 4.6, C - How many network communication interfaces between MDDC Program network infrastructure and other network infrastructures existing today? |
| Although contained within a separate network enclave, the UTDAN and CTDAN ‘ride’ upon the MDA UNET and CNET network infrastructure as detailed within the Industry Day brief located on FedBizOpps.gov. In this aspect, these MDDC networks are dependent upon MDA infrastructure. There is connectivity from those networks via FTP and Hypertext Transfer Protocol Secure (HTTPS) to allow for transfer of data. The MJAT network, while managed by the MDDC Program, is a part of the MDA Classified Network (CNET) connecting directly to that network. |
The TSS systems and networks connect to, and ride upon, the Pacific Range Support Team (PRST) network and use the Defense Research Network (DREN) as a backup.
| 92 |
| SOW 4.6, F - How often are the periodic DR tests? |
| Annually |
| 93 |
| SOW 4.6, G - Does a SPOC help desk exist today, if so how many contacts does it receive monthly. |
| Yes, for IT related issues. Not all calls are logged – minor issues (password reset, etc.) that are immediately resolved, are not logged into the Helpdesk system, these incidents average around 160/month. Issues that are escalated beyond that point are recorded. These incidents average approximately 50/month. |
| 94 |
| When is CDRL A020 Transition Plan due? |
Since transition occurs at the start of contract, will the Transition Plan be submitted with the proposal? No due date information was provided in the CDRL for Data Item 020.
Yes, a Transition Plan is a part of the proposal. The transition plan required by CDRL 0020 will be as required during the performance of the contract.
| 95 |
| NOTE 2 states a doctorate degree may be substituted for 25 years experience. |
Is this correct since under NOTE 1 it states a doctorate degree may be substituted for 10 years experience?
Attachment 3, Govt Labor Categories, NOTE 2 for the Minimum Qualifications matrix on the last page of the document, will be corrected to state a doctorate degree may be substituted for 10 years experience.
| 96 |
| 2d sentence states, “Contractor shall provide all necessary material, labor, equipment and facilities incidental to performance of this requirement.” |
Could the Government clarify the extent of facilities necessary to support the requirements?
The contractor will provide facilities for TSS operations (TEDAC, TGRS, TM Ops). These systems currently reside at their respective contractor facilities. The winning Offeror would be required to provide similar capabilities.
| 97 |
| General comment. Block 5 “contact reference” lists a SOW paragraph that appears not to map correctly. |
Could the Government clarify the SOW paragraphs aligned with the CDRLs?
Exhibit A, CDRL DD Form 1423, Block 5 for all Data Items except Items 013 through 016, will be corrected to show the correct SOW references.
This is the start of the file's text. The full file is on GovTribe.