Annex_E_Data_Collection_Questionnaire.xlsx

Instructions

<System>-<PEO/SEC>-<Date>-<Version>-<Status>

&"Arial,Bold"&12Software Maintenance Data Collection Questionnaire

&F

System-Level - Context

Administrator: Program Name - Enter the name given to the acquisition program, information system, or effort/initiative. If the system is part of a larger Program-of-Record (POR), enter the system name here, and provide an explanation of how it relates to the POR in the system description.

Administrator: System Description - In a few words, provide a top-level system description of the final overall product maintained or to be maintained. For example: two engine attack helicopter, landing craft used to transport heavy equipment from ship to shore.

Administrator: Current Phase/Milestone - Enter the current Phase/Milestone for the program. If a system is in multiple phases concurrently, select the highest applicable phase. For example, if a system is in O&S, is in O&S, but also has some new development work ongoing, select O&S, and put a note into the comment field in section 1.6.14.

Pre-A: Material Solution Analysis Phase A: Technology Maturation and Risk Reduction Phase B: Engineering and Manufacturing Development Phase C-LRIP: Production and Deployment Phase - Low-Rate Initial Production C-FRP: Production and Deployment Phase - Full-Rate Production O&S: Operations and Support Phase

cheryl.jones5: Number of Unique Hardware Variants. Provide the number of unique hardware variants that are supported by this software.

Administrator: Maintenance Profile - Describe whether the system is doing mainly capability enhancements, maintenance, cyber-security, or other changes.

Administrator: Operational Tempo - Select the highest operational tempo for the field units using this software. Entries may be:

Extensive: Full-time use of the system; system is central to mission accomplishment.

Regular: Routine, but less than full-time, use of the system.

Event-driven: Occasional use of the system.

Other: Please describe.

Administrator: Software Process Maturity - Report the characterization of the maintainer’s software process maturity using a methodology such Carnegie Mellon’s Capability Maturity Model Integration (CMMI), or an alternative equivalent rating. The reported software process maturity should reflect the rating that the primary maintenance organization has formally certified as of the date of the reporting event. The date format is month, day, and year MM/DD/YYYY.

• If no formal certification has been conducted, enter as “none”. If a single submission is used to represent the work of multiple organizations, enter the level of the organization that will be expending the most effort on the maintenance project.

• If the Government has accepted an alternative assessment mechanism, such as the Air Force’s Software Development Capability Evaluation (SDCE) or ISO/IEC 15504, enter those results and explain the meaning of the assessment.

Administrator: Data Rights - What type of rights does the system have? Select one of the following:

Unlimited Rights. Developed exclusively at Government expense, and certain types of data (e.g., Form, Fit, and Function data [FFF]; Operation, Maintenance, Installation, and Training [OMIT]). These rights involve the right to use, modify, reproduce, display, release, or disclose technical data in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so.

Government Purpose License Rights. This right involves the right to use, duplicate, or disclose technical data for Government purposes only, and to have or permit others to do so for Government purposes only. Government purposes include competitive procurement, but do not include the right to permit others to use the data for commercial purposes.

Limited Rights. A limited rights agreement permits the Government to use proprietary technical data in whole or in part. It also means that the Government has to obtain the expressed permission of the party providing the technical data to release it, or disclose it, outside the Government.

Restricted Rights. Developed exclusively at private expense.

Specifically Negotiated License Rights. This right pertains whenever the standard license arrangements are modified to the mutual agreement of the contractor and the Government. In this case, the exact terms are spelled out in a specific license agreement unique to each application.

Multiple Data Rights. Use this category if different software elements (components) have different data rights, and then explain which data rights are applicable to which software elements in explanation field in 1.6.12.3.

Administrator: Appropriations - Indicate all type(s) of appropriation used to fund the contract or the particular contract line item being reported.

Research, Development, Test and Evaluation (RDT&E) Production Operations and Maintenance (O&M) Overseas Contingency Operations (OCO) Other Program Allocation (OPA) Foreign Military Sales (FMS)* Other (please describe) *For FMS cases, please indicate if FMS dollars are part of project. If FMS dollars are "fair-share" of system dollars (contribute a portion of project costs), then include them in the dollars reported in the rest of the form. If FMS dollars are used for separate hardware or distinct releases, then include that in a note in the comment section and not include the dollars in the remaining sections.

Data Collection Questionnaire

For Official Use Only

System-Level - Annual

Administrator: System-Level Data - For effort and cost data, actual data is preferred. If effort hour data is not available, provide hours based on Full Time Equivalent counts per year, using engineering judgment. Multiply the FTE count by the average hours per year to provide hours. Cost can then be calculated by multiplying hours by the average labor rate per person. In this case, add an appropriate note in the comment field in each section.

If you don’t have actual data or FTE data, please provide planning data and make a note in the comment field in each section. If data is not available, use the responses defined in the Instructions tab (N/A, Zero, Unavailable).

Report all effort data in hours (not FTE counts - translate those into hours). Report all cost data in dollars (not thousands of dollars). If any other unit of measure is used, please record that in the comment field.

In the comment fields, for each WBS elements, please provide the appropriate data source used, information on how the data is collected and the level at which it is collected, as well as any additional information that would better explain the above data. For example, describe whether the system tracks release data separately, and if the contractor collects effort/cost data at a detailed WBS level. Some examples of data sources are, but not limited to: Cost Reports, GFEBS, engineering judgment, etc.

Please enter a response in every field.

2.1 Fiscal Year

Administrator: Fiscal Year - Provide the fiscal year for which the cost data below applies. Use a separate column for each year.

2.2 Total Effort and Cost

Administrator: Total Effort and Cost Data - All effort and cost associated with the software system for the year. This should be the sum of all other data, including the portion of the release data spent in the specified year (total of the WBS elements in sections 2.3 to 2.10 plus 3.4).

Administrator: Number of Project Mgt: Hours Expended - Government Provide the number of government labor hours that were expended in project management.

Administrator: Software License Management Effort and Cost - Cost and effort associated with the procurement and renewal of software licenses for NDI, COTS, GOTS, or open-source software. This data is for managing licenses for the maintenance facility as well as deployed systems. The effort and cost for configuring and integrating the licensed software is reported separately in the release data.

Administrator: Software License Details - Provide cost information on each software license used by the system. Provide the details of the current set of licenses, on the tab entitled “Software Licenses”. These include licenses for the maintenance facility as well as deployed systems. List all applicable licenses, and the cost the last time it was purchased. There can be two rows for each license: one for the right-to-use license, and one for the maintenance agreement. For any enterprise licenses, the cost data can be marked "unknown".

2.6 Certification & Accreditation (C&A) Effort and Cost

Administrator: Certification & Accreditation (C&A) Effort and Cost - Effort and cost associated with verifying a software system against externally defined domain performance criteria for this release. These activities include preparing for and managing certification and accreditations. Activities include Cyber-Security (including Risk Management Framework, DIACAP, IAVA), Interoperability testing, Common Operating Environment testing, Safety, Airworthiness, and Networthiness.

Administrator: System Facilities (SF) Effort and Cost - Effort and cost associated with establishing, operating and sustaining software development facilities. Facilities include government and contractor acquisition, development, maintenance, test, and external test facilities. Test facilities may include test facilities at the PEO or SEC, the contractor, the C&A organization, interoperability test facilities, IOT&C facilities, and operational test facilities. In the comments section, provide a list of all facilities used, even those which are paid for separately and not included in this system’s data (note that they are paid for separately).

Administrator: Sustaining Engineering (SE) Effort and Cost - Effort and cost associated with engineering (e.g. system specific test support, investigations, PM support) and user support (e.g. user training, help desk, software delivery). SE does not include any effort or cost for either maintenance (corrections) or capability enhancements: these are included in the release data. User support should not include FSEs, nor data in other sub-categories.

Administrator: Field Software Engineering (FSE) Effort and Cost - Effort and cost associated with the on-site support of a deployed software product or system in its operational environment. FSE duties may include on-site technical assistance, problem troubleshooting, software installation, operational assistance, or on-site training. If FSE personnel are used, but paid for by another organization, put “unknown” into the hours/cost and a description of who pays for that personnel into the comment field (if the FTE equivalent is known, please provide that data in the hours field).

Administrator: Operational Management (OM) Effort and Cost - System-level effort and cost allocated to pay for OM resources. This may be done as a tax, within overhead, or through inclusion of certain OM resources. OM resources are those associated with establishing and operating the organizational infrastructure required to implement common software maintenance business and technical processes across multiple software systems. These activities include operations, organization management, personnel management, financial management, information management, process management and change management.

Data Collection Questionnaire

Release-Level

Administrator: Release Schedule/ Cost/ Size Data - For a delivered release or an engineering release that has gone through Final Qualification Test, provide for the cumulative actual values. For a partial release, provide the planning data including the estimate to complete for the remaining work, as well as the cumulative-to-date actual values.

In the comment fields, please provide the appropriate data source used, where applicable, along with any additional information that would better explain the above data. Some examples of data sources are, but not limited to: Cost Reports, GFEBS, USC Code Counting Tool, CM tools such as DOORS, etc.

Each column in the data collection form is used to record data for one release regardless of release type (explained in section 3.1.3).

If a release contains only IAVA fixes, fill out rows 3.1 to 3.4 (excluding 3.2.5) and 3.9 only. If your release has updates in additional to IAVAs, then fill out the full worksheet. Short IAVA releases that are done monthly may be aggregated into quarterly releases, for the purposes of this data collection.

Provide the data for any release that were completed in FY13, FY14, and FY15.

Report all effort data in hours (not FTE counts - translate those into hours). Report all cost data in dollars (not thousands of dollars). If any other unit of measure is used, please record that in the comment field.

Administrator: Other - Other changes that do not fall into the above categories. Please explain in 3.1.4.

Administrator: Release Status - Enter the state of the release for which the data is being collected:

Partial: Any release close to being delivered and contains actual data to-date along with planning data for the entire release.

Final: A delivered release and contain all planned and actual data for that release.

Administrator: Operating Environment - Identify the operating environment in which the maintained software system operates:

Surface Fixed: Software is embedded in a system at a fixed site.

Surface Mobile: Software is embedded in a system that is moved somewhere and setup.

Surface Portable: Software is embedded in a handheld or portable device.

Surface Vehicle: Software is embedded as part of a moving vehicle.

Air Vehicle: Software is embedded as part of an aircraft.

Sea Systems: Software is embedded as part of a surface or underwater boat/ship.

Ordnance Systems: Software is embedded as part of a missile or rocket.

Space Systems: Software is embedded as part of a spacecraft.

Administrator: Application Domains for Release - For the work being done on this release, identify all relevant application domains that apply by entering the approximate percentage of effort relative to total release effort expended (or planned) for this release. The total percentage should add to 100%.

Administrator: Microcode and Firmware % - Firmware/microcode is software is stored on target hardware devices that do not have hard disks and use programmable logic devices. It is a combination of persistent memory and the program code and data stored in it.

Administrator: Total Release Effort and Cost - Report the total expended effort and/or dollar cost for the release to implement software changes. This includes all hours and cost associated with changing software to maintain the operational capability of the system. It includes all hours associated with addressing/correcting errors, addressing, cyber-security issues and changing software, including requirements analysis, design, implementation, and software testing (including IV&V). Provide this data for each organization working on this system.

If you don’t have actual expended data, please provide data based on equivalent FTE data multiplied by the average labor hours per person year. If you do not have FTE data, please provide planning data. In either case, make a note in the comment field in each section.

Administrator: Requirements/Interface Size Reporting - In the following sections, there are multiple size measures. Provide the data that is relevant to your system.