Q A_III.docx

1. Do the CMMI appraisers have to be certified at Level 3 or 5?

Staffing should consider both. The labor categories list a CMMI High Maturity Consultant. This category would anticipate being utilized for CMMI appraisal purposes, including a high-maturity appraisal; therefore a certified High Maturity Appraiser will be required. However, past history of contracting needs indicate typical CMMI appraisal services provided to customer sites are at ML3 or below.

2. To provide notional hours, is there an estimate of number of task orders coming out over 5 years?

The Government will be using the notional hours for the evaluation. The values used will not be released.

3. Is the government looking to get CMMI certified?

Yes - various government sites are interested in obtaining CMMI certification at targeted CMMI maturity and capability levels.

4. What kind of applications will be in scope?

System and Software development and maintenance applications, specific to government embedded systems at various customer sites. The specific applications being utilized and background information will be included within individual task orders, per defined requirements.

5. What is the technology architecture and platform for these applications?

Primarily Government embedded weapon systems at various customer sites. The specific platforms being utilized and background information will be included within individual task orders, per defined requirements.

6. How many different locations from where these applications will be developed?

Multiple Government sites, primarily at DoD installations, within the continental US. However, this contract will assist other government organizations outside the DoD, to include the FAA, DHS, NASA, etc. The specific platforms being utilized and background information will be included within individual task orders, per defined requirements.

7. Is it a centralized or distributed data centers/hosted environment for the application?

Both centralized and distributed. The specific data structures and systems being utilized and background information will be included within individual task orders, per defined requirements.

8. Is that true that government is expecting a 20 page response for a price proposal? Is there a typo?

20 pages are allowed. All labor categories will need to be included in the price proposal and our current list is 13 pages.

9. Is the documentation of the best practices part of contractor responsibility or agency responsibility?

Documenting Best Practices is the responsibility of the Government customer sites. The consulting functions typically evaluate, train, assist, mentor, advice, review, consult, etc. It is not anticipated the contractor will actually document best practices for the government organization.

10. The sample PWS is too high level. Can the Government provide more specific tasks and details regarding the type and scale of effort(s) (e.g., web development, SharePoint, application development, or something else) to support for the PWS in order to scope the effort and provide a more accurate technical response.

The PWS is intended to be high level to ensure the awardee can fulfill all potential tasks. Specific tasks will be defined with each task order.

11. We understand that one aspect of the PWS is to setup a dev environment, but for how large of a project, how many developers, are they local or remote. These details such as type(s) of projects being supported, size and scope, number of personnel involved, and the support role required from the contractor (e.g. project management, development, architecture, assessment, helpdesk support, training, etc.) will help us scope the technical response more accurately.

The PWS establishes requirements for the Contractor to join a Government technical team as expert consultants and advisors in the creation of a development environment, not to actually create the environment. The development environment will be created and hosted by the government. The PWS states: “This includes expert consulting, technical support and recommendations regarding system software design and architecture, software interfaces, application-level software code, software processes and behaviors of the program systems, and technical documentation.”