Section_J _Attachment_19_-_SEMS_III_Annual_Sustainment_PWS_V1.3_13_May_13.docx

FA4600-12-R-0013-0002

Section J, Attachment 19

AIR FORCE WEATHER (AFW)

SYSTEMS ENGINEERING, MANAGEMENT AND SUSTAINMENT III (SEMS III)

ANNUAL SUSTAINMENT

PERFORMANCE WORK STATEMENT (PWS)

7 Jan 13

REVISION/CHANGE RECORD

1.0 DESCRIPTION OF SERVICES

1.1 PURPOSE

1.1.1 This PWS specifies systems engineering, program management/systems management and systems sustainment functions required to support Air Force Weather (AFW). It is meant to communicate AFW’s expectations of Contractor performance in conducting upgrades, refreshes, technology insertions and sustainment of AFW’s systems. The Contractor’s performance shall be evaluated on the basis of agreed to performance measurements - metrics. The metrics focus on desired outcomes and not interim process steps. Interim process steps are delegated to the Contractor who shall manage the processes and practices used to achieve contract outcomes. Using an outcome focus communicates that Air Force Weather Agency (AFWA) intends to give the Contractor the flexibility to continuously improve and innovate over the course of the contract as long as the critical outcomes expected are being achieved.

1.1.2 The mission of the AFWA is to arm our nation’s forces with essential air and space environmental intelligence, training, and technical services to ensure battlespace awareness and decision superiority. The AFWA Strategic Center and the 14th Weather Squadron produce weather products for US combat forces, the combatant commands, all Air Force major commands, all Army major commands, and other agencies as directed by the Chief of Staff, USAF. AFWA collects, quality controls, and processes worldwide meteorological data to provide a wide range of tailored military products describing the present and future states of the aerospace environment. The Contractor, meeting AFW’s expectations described below, shall provide the systems sustainment, and program management/systems management necessary for AFW systems to be available to support AFW’s and AFWA’s mission(s).

1.2 SCOPE

1.2.1 The primary goal of the Contractor is to ensure that AFW systems deliver an increasingly higher level of effectiveness, reliability and performance (technically, functionally and in terms of customer support) while reducing ownership costs. The Contractor shall be dedicated to providing world-class, industry standard information technology capabilities. Since sharing information rapidly, reliably and effectively while maintaining proper security integrity is critical to the AFW mission, the Contractor shall maintain the highest quality services and customer support, as an extension or as an enhancement to current capabilities. The Contractor is expected to be a partner with AFW personnel and a proactive catalyst in continuously improving the effectiveness of AFW systems and the products these systems provide to AFW customers in supporting current and emerging missions. The Contractor is expected to bring the tools, experience, practices and leadership to AFW to move its information technology environment into a proactive, highly customer responsive system following best business practices. (Note: Those services deemed mission essential are designated following the number of each paragraph describing the performance of that service with the symbol (ME).)

Attachment 1, SEMS III Contract PWS lists the reference documents for Government policies and procedures. The documents identified in Atch 1, SEMS III Contract PWS are for reference only. This PWS will identify those documents that are compliant by stating the document number and/or title with applicable paragraphs or in entirety designation.

Attachment 2 to this PWS shows the mapping of this PWS’s paragraphs to Contract Line Items.

Unfunded requirements are identified in attachment 3.

Attachment 4 states the Government requirements which are evaluated using the SEMS III Incentive Fee Plan.

Attachment 5 provides changes as needed to the SEMS III Incentive Fee Plan.

Attachment 6 is used by the Contractor to identify baseline costs by system to be used to evaluate Incentive Process Objective PO-2: Lower Annual Total Enterprise Life Cycle Cost during full contract performance.

2.0 REQUIREMENTS

2.1 Systems Engineering

2.1.1 The Contractor shall perform design, development, integration, test, and implementation for task orders to expand capabilities by upgrading, modifying, extending the service life and inserting new technology into the AFW systems. To perform task orders, the Contractor shall implement a system engineering process and document in the Systems Engineering Management Plan (SEMP) for all task orders. The Contractor shall describe and reference the software development processes and procedures (e.g. checklists, templates) to be used to execute task orders in the Software Development Plan (SDP). This plan shall include processes for software management, development and unit test, software modification and unit test, hardware integration, commercial off-the-shelf (COTS) integration, and implementation and installation. These software development processes shall reflect processes that meet or exceed Capability Maturity Model Integration®-Development maturity level 4, version 1.2. The Contractor shall document its test processes in the SEMP and the SDP as appropriate. The Contractor shall describe the processes that identify the technical impacts of the design, development, test and implementation/integration to the AFWA enterprise in the SEMP and SDP as appropriate. The Contractor shall describe in the SEMP and the SDP how its processes shall attain the objective threshold values contained in the Services Summary. System engineering and software development services required are in the SEMS III Contract PWS. (CDRL A013, A049)

2.1.2 The Contractor shall document design processes including cost estimation processes in the SEMP and the SDP as appropriate.

2.1.3 Reserved

2.1.4 The Contractor shall describe system and software development and implementation processes in the SEMP and SDP as appropriate.

2.1.5 The Contractor shall document test processes in the SEMP and SDP as appropriate.

2.1.6 The Contractor shall participate in Weather Data Analysis (WDA) Test IPT and Combined Test Force meetings. The Contractor shall identify AFWA existing system test requirements to support WDA integration testing. The Contractor shall jointly conduct enterprise-level acceptance testing of WDA components and legacy interfaces with Government agencies. The Contractor shall provide a report of test results. (CDRL A005, A006, A028)

2.1.7 The Contractor shall describe System Security Engineering processes in the SEMP.

2.1.8 The Contractor shall develop, implement, and maintain the Configuration Management (CM) process for developed and sustained CIs as specified by task orders. These CM processes shall be captured in the CM Plan that includes configuration control, configuration status accounting (CSA), configuration verification and audit, and configuration identification for all systems and software CIs. (CDRL A015)

2.1.8.1 Reserved

2.1.8.2 Reserved

2.1.8.3 Reserved

2.1.9 Reserved

2.1.10 The Contractor shall conduct and deliver to the Government an annual power study of the AFWA Uninterruptible Power System (UPS) in Bldg 185 to include load distribution. The report is due 30 days after completion of Contractor study. The Contractor shall conduct and deliver to the Government an annual assessment of the adequacy of existing power in all enclaves. This second report is due 30 days after the completion of the Contractor assessment. (CDRL A001)

2.1.11 The Contractor shall apply the systems engineering process to investigate, and analyze candidate operational concepts and technology enhancements. The Contractor shall technically evaluate the feasibility of implementing new technologies. The Contractor shall evaluate Government proposed system life extension and performance enhancement programs; the emphasis shall be to increase operational readiness while reducing ownership cost through use of industry standard products. The Contractor shall analyze and assess Government proposed AFW modifications and upgrades and associated system specification changes. The Contractor shall assess communications bandwidth adequacy and future bandwidth requirements. The products of engineering analysis may be impact assessments, cost estimates, engineering analysis, technical and cost tradeoffs, and sustainment requirements identification. (CDRL A001)

2.1.12 Reserved

2.1.13 Reserved

2.1.14 Reserved

2.1.15 Reserved

2.2 Program Management/Systems Management

2.2.1 The Contractor shall provide the technical approach, organizational resources and management controls to be employed to meet the cost, performance and schedule requirements for task orders during the contract period of performance in a Program Management/System Management Plan (PM/SM). The PM/SM Plan shall describe the approach for managing and controlling contract costs, including identifying associated checks and balances. The PM/SM Plan shall describe the approach to accommodate varying staffing requirements over the life of the contract, including long-term, ongoing tasks, special efforts of lesser duration, and rapid replacement/addition of personnel in the event of emergencies/contingencies. The staffing approach shall address special requirements such as clearances and professional certifications. The PM/SM Plan shall describe the approach for personnel recruitment and retention. The PM/SM Plan shall identify the Contractor program manager’s responsibilities and authorities, and interfaces between Contractor and Government and between Contractor and other Contractors. The PM/SM Plan shall describe training to be provided to employees. The PM/SM Plan shall address how the Government will be informed of cost, schedule including key milestones, and performance status for each task order. The PM/SM Plan will identify the tools the Contractor intends to use in meeting contract and task order requirements. The Contractor shall describe in the PM/SM Plan how its processes shall attain the appropriate objective threshold values contained in the Services Summary. The Contractor shall conduct all program management/system management activities for all task orders in accordance with the Program Management/System Management Plan (PM/SM). The Contractor shall provide all personnel, equipment, tools, materials, supplies, parts, test equipment, and supervision to meet the requirements of task orders. Personnel shall possess necessary professional certifications commensurate with tasks assigned. The Contractor shall identify all personnel performing an Information Assurance (IA) Technical role (i.e. System Administration) and IA System Architect and Engineer (IASAE) Specialty (i.e.., System Engineering) as stated in DoD 8570.01-M (sections C1.4.4.5, C1.4.4.12, C2.1.5, C3.2.4.8.3, C3.2.4.8.4, C7.3.4, C10.1.2, C10.2.3.1.1, C10.2.3.1.2, C10.2.3.3, and C10.2.3.7). and AFMAN 33-285 (section 1.1, 1.3, 1.4.19.8, 2.3.1.1, 2.3.3, and 4.3.3.). The Contractor shall provide name, IA Level (i.e., Technical Level 1-3 or System Engineer Level 1-3), role (i.e. system administrator or system engineer), certification obtained, and date certification obtained. This shall be provided on an annual basis and whenever personnel changes. The Contractor shall provide this report within 60 days of start of full contract performance and annually on 30 Sep. The Contractor shall continually monitor cost, schedule including key milestones, and performance under this contract and immediately notify the Contracting Officer of any problems noted. The Contractor shall provide any additional cost and schedule information as requested by the Contracting Officer. The Contractor shall manage the business and financial data for its activities by using an Earned Value Management System (EVMS). The EVMS shall track and report Schedule Performance Index (SPI), Cost Performance Index (CPI), inception to date and cumulative costs. The Contractor shall also report their estimate at completion for each tracked item and for the contract as a whole. These reports shall be delivered with the Contract Performance Report (CPR). The Contractor shall develop a Performance Measurement Baseline (PMB). The PMB shall be traceable to the Contract Work Breakdown Structure (CWBS) and task orders and shall include time-phased budget and forecast expenditure profiles. Appropriate PMB data shall be included in the monthly status report. The Contractor shall revise the PMB in a timely manner for Government-approved contract changes. The Contractor shall provide a monthly Contract Performance Report with information for each open order. The Contractor shall modify as necessary, implement, and maintain the Government provided CWBS that clearly defines how the contract will be managed and controlled. All performance and financial reports shall be based on the CWBS. The Contractor shall update and deliver the sustainment model each time a system has a design, baseline change or implementation that changes system life-cycle sustainment cost, and at the beginning of each contract period of performance. The Contractor shall communicate status information and issues to the Government in a clear and timely manner. The Contractor shall conduct a weekly program management meeting with the Government. At this meeting, the Contractor shall present summary of current activities, project schedules including key milestones, upcoming and in-process contract changes, action item status, project dependencies (including Government support responsibilities), risks, and previous meeting minutes. The Contractor shall maintain schedules in Microsoft® Project. (CDRL A001, A007, A008, A009, A019, A031)

2.2.2 The Contractor shall develop and brief a monthly status report to include personnel employed, activity schedules, key milestone status, financial status, system engineering activities, program management/system management activities, and system sustainment activities. The Contractor shall develop an integrated set of management indicators such as cost, schedule and performance status. These indicators shall be included with each monthly status briefing. The Contractor shall relate these indicators to mission accomplishment. The monthly status report shall compare the actual performance to the plan. There shall be a summary of the status of each task and subtask on contract. It shall include major milestones, progress for each milestone to date, contractor’s assessment of progress, and any roadblocks or help needed. It shall include clear and descriptive variance statements (cost and schedule) for current and cumulative periods when WBS variance exceeds 10% of plan (current and/or cumulative) and is greater than $10K. The monthly status report shall present performance on subtasks, milestones achieved/scheduled, subcontractor deliverable status, CDRL timeliness against plan, deliverables delivered, status of deliverable comment implementation and time to accepted, Government furnished equipment (GFE)/Government furnished information (GFI) receipt status, risk distribution, a risk overview including the identification numbers of the risks and the list of the risks, metrics, program issues, status of corrective actions, and upcoming events summary. The monthly status report shall contain an integrated master schedule (IMS) containing: engineering study milestones, baseline and updates to the IMS including columns (e.g. Start1, Finish1) to maintain the originally planned start and finish fields as the baseline, and reflect the current plan; key milestones and activities; subcontractor deliverables and dependencies; and GFE, GFI deliveries and dependencies. The Contractor shall develop, update and brief an IMS containing all critical milestones, critical path activities, prerequisite events and activities and their interdependencies for each task order. The Contractor shall brief the monthly status report to Government program management/contracting officer’s representative personnel, and the AFWA Commander. The financial portion of the monthly status report shall be briefed at a separate meeting. (CDRL A009, A031)

2.2.3 The Contractor shall recommend processes rated to meet Capability Maturity Model Integration® for Development level 4, version 1.2 in the PM/SM Plan. If the Contractor’s recommended processes are not independently rated to level 4 or better at time of contract proposal submittal, then the Contractor shall submit in the PM/SM Plan the proposed steps to achieve level 4 rating of process maturity. Achievement of at least independently verified level 4 rating of process maturity for recommended processes should occur no later than 6 months after the date of contract award announcement. (CDRL A008)

2.2.4 The Contractor shall develop and maintain the Data Management processes for all task orders and document in the Data Management Plan. This includes recommending actions that minimize the cost of data to the Government while maintaining baseline integrity. The Contractor shall permit the Contracting Officer or an authorized representative at a reasonable time access to all records and data used in the performance of this contract. Access shall be granted within five workdays of the request. The Contractor shall create and maintain a data management and maintenance system in the Management Information Systems that:

a. Prevents duplication of data previously developed.

b. Assures the data developed meets contract and task order requirements.

c. Ensures contract data is delivered in a timely manner.

d. Ensures data being delivered is the latest revision.

e. Provides data in native format to enable manipulation for future Government uses.

f. Ensures on-line access is readily available and easily accessible from Government offices at no additional cost to the Government.

g. Maintains a current status of all contract and task order data requirements.

(CDRL A040)

2.2.4.1 Management Information System (MIS)

The Contractor shall establish and maintain a MIS, to include any existing databases and technical documentation required to support this contract, in the Continental U.S. which is accessible from both Government facilities and to all authorized users of this system. The Contractor shall maintain data in this exchange, to the maximum extent practicable, in electronic format. The Contractor shall ensure all data generated in the performance of this contract is made available via the MIS including technical records, reports, files and other documentation. The MIS shall include schedule status, action items, risk status, action item status, metrics and key technical documents. The Contractor shall publish a monthly listing of all data added or removed from the MIS for all task orders. The Contractor will not use a proprietary product for the MIS and will use the existing Government enterprise tools. A repository of electronic and/or hard copy data could include, but not be limited to, the following types of data:

a. Programmatic documents including referenced documents.

b. Equipment drawings including 3-dimensional floor layouts and assembly drawings, schematics, and wire lists defining assemblies to the lowest assembly level.

c. Current baseline specifications and all changes since baseline to include system, configuration item, and software specifications.

d. Installation documentation: e.g., equipment arrangement drawings, site plot plans, cable and wiring lists, cable interconnection diagrams, and technical power distribution as required.

e. Technical Manuals.

f. Software documentation and media.

g. Software database documentation and media.

h. Integration and Operational Test plans.

i. Training System Development Plans.

j. Supporting and ancillary documents such as:

1) Data Lists.

2) Reports, Studies, and Analyses.

3) Interface Control Documents.

4) Interface Requirements Specifications.

5) Interface Design Documents.

6) Test Documentation.

7) Engineering Support Plans.

8) Logistic Support Plans.

9) Specification Change Notices.

10) Logistics Analysis Reports and Documentation.

11) Cost data.

k. Technical Manual development plans.

l. Training Materials and Documentation.

m. Power requirements.

n. Lessons learned/checklists.

o. Configuration Change request records.

p. Quality assurance evaluation records.

q. COTS software media, licenses and subscription services.

r. List of deferred requirements.

(CDRL A029)

2.2.4.2 The Contractor shall ensure that all Contractor-generated technical records, reports, files, and other documentation are made available to the Government through the MIS during the performance of this task order. The Contractor shall obtain approval from the Government’s Contracting Officer Representatives (CORs) before releasing any information outside of the Department of Defense that has been stored, generated, or archived related to this task order. The Contractor shall ensure the Government retains all reproduction rights to all data. The Contractor shall clearly mark all records, files, reports and data deemed proprietary by the Contractor in accordance with 2.2.4.3. The Contractor shall inform the Government of the need to use a proprietary marking before doing so. The Contractor shall publish a monthly listing of all data added or removed from the MIS for all task orders. (CDRL A029)

2.2.4.3 Documentation developed or acquired may include existing data only if such data has been provided to the Government with unlimited data rights as defined by DFARS clause 252.227-7013, Rights in Technical Data/Non-Commercial Items or DFARS clause 252.227-7014, Rights in Non-Commercial Computer Software and Non-Commercial Computer Software Documentation, as incorporated in Section I, DFARS clause 252.227-7017, Identification and Assertion of Use, Release or Disclosure Restrictions, DFARS clause 252.227-7019, Validation of Asserted Restrictions – Computer Software, DFARS clause 252.227-7027, Deferred Ordering of Technical Data or Computer Software or DFARS clause 252.227-7037, Validation of Restrictive Markings on Technical Data. The Contractor may choose to document its own subcontractors, and vendors existing COTS hardware; however, the Contractor must comply with the requirements in 252.227-7013, 252.227-7014, 252.227-7017, 252.227-7019, 252.227-7027, and 252.227-7037, and notify the Contracting Officer prior to committing to the use of privately developed items, components, processes or computer software to be delivered with other than unlimited rights. If at any time other than unlimited rights are proposed for delivery under this contract, the Contracting Officer reserves the right to negotiate the minimum technical data rights required under this task order. Changes for Government technical orders will be in accordance with the tailored Technical Manual Contract Requirements consistent with the style and format of the original document. This includes systems administrator guides, AFTO 22 Technical Order Improvement and Reply submissions, and operator handbook development/updates.

2.2.5 A DD Form 254 attached to the contract provides more specific security requirements. The Contractor shall be responsible for obtaining and maintaining the proper clearances for Contractor personnel. The Contractor personnel shall have the required security clearance prior to arrival on-site to perform under this contract.

2.2.5.1 The Contractor shall comply with DoD 5220.22-R (Industrial Security Regulation), and other pertinent instructions, directives, and regulations, as provided by the Government, to ensure the proper implementation of the Contractor’s industrial security program. This includes clearance procedures, visitors, inspections, violations, education, classification, international security programs, and operations security. Facility and employee security clearances are obtained according to DoD 5220.22-M (National Industrial Security Program).

2.2.5.2 The Contractor shall escort visitors through the facilities at the request of the Government’s CORs. All requests for non-duty access shall be coordinated through the Government’s CORs. The Contractor shall provide in writing to the Government’s CORs a point of contact for access during non-duty hours. Point of contact designation is due at the beginning of full contract performance and updated the next duty day after change of appointment. In case of an actual emergency during non-duty hours and when time does not permit due to the nature of the emergency to contact the Contractor for access, the Government’s CORs or other Government personnel may provide access to the designated Contractor facilities for emergency personnel if the Contractor cannot be reached. (CDRL A001)

2.2.5.3 The Contractor shall control and provide access to their designated areas at HQ AFWA 24 hours per day, including Saturdays and Sundays for Government personnel on an on-call basis. Access for other Contractors in performance of modifications, maintenance and inspections will be provided during times agreed to by the Government’s CORs and the Contractor.

2.2.5.4 The Contractor shall comply with restricted areas procedures and instructions. Certain buildings and other facilities on Offutt AFB are “off-limits” or restricted to the general public. Contractor personnel shall not enter any “off-limits”, restricted facilities or areas within AFWA’s building on Offutt AFB without specific permission.

2.2.5.5 The Contractor shall establish and implement a physical security plan for all task orders. The Contractor’s physical security plan shall comply with requirements of AFI 31-101: Integrated Defense, and the 55th Wing Integrated Defense Plan. The Contractor shall define procedures to provide internal safeguards for the security of all Government-furnished property and all property in the possession of the Contractor for the performance of required services. (CDRL A020)

2.2.6 The Contractor shall assess all task orders and provide risk assessments. The Contractor shall document risk management process in the PM/SM Plan. The Contractor shall identify risks and develop risk mitigation strategies to ensure task orders have the greatest probability to achieve objectives. While assessing a project for potential risks, the Contractor shall also identify opportunities for improving schedule, increasing functionality and performance, and for cost savings that would mitigate potential risks. As part of risk assessment, the Contractor shall provide dependency and interrelationship identification, and integrated system/project schedules. The Contractor shall use and maintain a risk management tool for documenting risks and risk mitigation strategies. The Contractor shall make this tool available to the Government on the MIS (see paragraph 2.2.4.1). The Contractor to the maximum extent possible will not use a proprietary product for the risk management tool and will provide the Government with the risk management tool at contract end. The Contractor shall conduct monthly risk management meetings, open to the Government, which will review risk items. There will be no delinquent risk mitigation actions. The contractor shall determine a risk probability, impact, and exposure value for each identified risk. The risk probability and impact values will be computing using guidance contained in the Risk Management Guide for DoD Acquisition. The exposure value will be calculated by multiplying the risk probability value by the risk impact value. The Contractor shall document meeting results and changes to risks and risk mitigation strategies. (CDRL, A008, A017, A030)

2.2.7 The Contractor shall establish, in conjunction with the Government, and maintain a system performance measurement process in accordance with the PM/SM Plan, and recommend system performance metrics to include security. The Contractor shall use well defined, outcome-based, metrics for metrics collection and analysis. The Contractor shall provide system performance monitoring and analysis to assess performance versus requirements to identify upgrade requirements with a goal of reducing ownership costs. The Contractor shall relate system performance to mission accomplishment. For any decrease in system performance incurred, the Contractor shall identify the probable cause(s) and submit any recommended corrective actions. The Contractor shall also include metrics that measure software reliability, for example the number of defects compared to the number of operational hours. In addition, statistical tools or models shall be identified to conduct software reliability assessments. For task orders which specify software development/maintenance tasks, the Contractor shall propose software reliability assessment tool(s), and seek concurrence with the Government for software reliability metrics and measures. The Contractor shall submit the corrective actions recommendations no later than 3 days after decrease in performance identified. The software reliability approach shall be described in the SDP. The Contractor shall generate a monthly performance report that describes system performance trends. As a minimum, the report shall include the following: metrics; trends – track performance metric categories over time; variances – track variance between metrics that target performance of actual vs. targets; lifecycle cost performance — includes cost performance data, both historical actual, and forecasted trends (forecast performance to target costs); and recommendations for improvement. The system performance measurement process and proposed metrics shall be documented in the PM/SM Plan. (CDRL A001, A008, A009, A049)

2.3 Systems Sustainment

2.3.1 The Contractor shall provide a sustainment approach using DoD, AF and AFWA directives as applicable to the task. The Contractor approach shall address hardware and software maintenance processes, license requirements, operational readiness rates and response times to meet operational capability needs in a cost-effective manner. The Contractor shall recommend the frequency and duration of the preventive maintenance required for the system. The Contractor’s focus shall be to maintain AFWA systems to meet required operational readiness rates while lowering ownership costs. The Contractor’s sustainment processes shall be documented in a Systems Sustainment Plan (SSP) and an Integrated Logistics Support Plan (ILSP) for all task orders. The Contractor shall describe in the SSP and ILSP how its processes shall attain the appropriate objective threshold values contained in the Services Summary. As defined in AFI 63-101, Attachment 1, Terms, software maintenance are those activities necessary to correct errors, add incremental capability improvements and adapt software to retain compatibility with hardware or with other systems with which the software interfaces. Also, software maintenance includes returning to operations software functions which do not perform as specified. As specified by task order, in performing software maintenance, the Contractor shall perform design, code, technical reviews, design reviews, integration, test, configuration management and implementations in accordance with contract PWS paragraph’s 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.8, 2.2.1 and 2.2.3. All anomalies and problems associated with sustainment shall be documented and monitored using REMEDY and established AFWA procedures. The Contractor shall follow the Configuration Change Request (CCR) process and ensure any and all changes are approved by the Configuration Change Board. The Contractor shall keep current Remedy information of (or other designated tool) hardware, software, (including what software is installed on each box), IPs and hostnames. The Contractor shall provide descriptions of all external interfaces, information being exchanged and protection mechanisms associated with each interface, all user roles required for access control and access privileges assigned to each role, unique security requirements including where they are implemented, the purpose and technical details of implementation (e.g. encryption strength/algorithm for data at rest), description of all categories of sensitive information stored and protection plans for each (e.g. privacy act, HIPAA), restoration priority of each subsystem, process or information source, and system/network connectivity diagrams. The Contractor shall utilize Remedy (or other designated tool) to keep current the status of TCNOs. All Contractor developed or modified software shall be scanned with a designated tool such as Fortify (or other designated tool) to identify any vulnerabilities. The vulnerabilities must be corrected by the Contractor. Results of scanning must be submitted to the Government. The Contractor shall deliver all trouble shooting aids, guides, and tools used in performing system sustainment. (CDRL A014, A023, A037, A050, A054)

2.3.2 (ME) The Contractor shall maintain all tasked systems specified in the following subsections (summarized in Table 1). (Table 2 reserved.) The Contractor shall ensure the system capability of all specified hardware and software meets or exceeds established standards as specified in the Services Summary. The Contractor shall provide normal (0730-1630, Monday through Friday) technical support as well as 24x7 on-call support (to include weekends and all holidays) for all AFWA systems tasked to maintain unless such support is specified as “Duty Hours” or “Best Effort”. “Duty Hours” and “Best Effort” support are defined in the Services Summary. In addition, annual hardware/software audits will be performed with the Government to include location of assets. NOTE: Cloud Depiction and Forecast System II, Data Pipe, Global Theater Weather Analysis and Prediction System, and Satellite Ingest application software baselines are under 2 WXG configuration management. (CDRL A039)

Table 1 Sustainment Requirements

Duty Hours

Duty Hours

Duty Hours

Duty Hours

24x7

Best Effort

X

24x7

X

24x7

2.3.2.1 (ME) The Contractor shall provide 24x7 hardware maintenance and system administration for the IBM AIX Production systems. This includes WDA servers, and data base servers.

2.3.2.2 (ME) The Contractor shall provide 24x7 hardware maintenance and system administration for the Red Hat Linux Hewlett Packard (HP) Production systems. This includes application servers, Anti-Virus Management System, Data Pipe servers, and Cross Domain Solutions systems.

2.3.2.3 (ME) The Contractor shall provide duty hours hardware maintenance and system administration for the IBM AIX Development and Test systems.

2.3.2.4 (ME) The Contractor shall provide duty hours hardware maintenance and system administration for the Red Hat Linux HP Development and Test systems.

2.3.2.5 (ME) The Contractor shall provide 24x7 hardware maintenance and system administration for the Oracle (Sun) Solaris Production systems.

2.3.2.6 (ME) The Contractor shall provide 24x7 software sustainment for HQ AFWA WDA delivered capabilities with the exception of the Joint Meteorological and Oceanographic (METOC) databases software. For Option Periods 1-3 only, the Contractor shall incorporate additional data types within existing database structures.

2.3.2.7 Reserved

2.3.2.8 (ME) The Contractor shall provide 24x7 software sustainment for the HQ AFWA Air Force Weather Web Services (AFW-WEBS) system.

2.3.2.9 (ME) The Contractor shall provide duty hour software sustainment for JIRA and Confluence software tools.

2.3.2.10 (ME) The Contractor shall provide duty hours hardware maintenance and system administration for the Oracle (Sun) Solaris Development and Test systems.

2.3.2.11 Reserved

2.3.2.12 Reserved

2.3.2.13 (ME) The Contractor shall provide 24x7 hardware maintenance and system administration for the Red Hat Linux High Performance Computing (HPC) HP Production system.

2.3.2.14 (ME) The Contractor shall provide duty hour hardware maintenance and system administration for the Red Hat Linux HPC HP Development and Test system.

2.3.2.15 (ME) The Contractor shall provide 24x7 hardware maintenance and system administration for the HQ AFWA Uninterruptible Power Supply (UPS) (Bldg 185).

2.3.2.16 (ME) The Contractor shall provide best effort hardware maintenance support for the HQ AFWA Geostationary Operational Environmental Satellite antennas.

2.3.2.17 (ME) The Contractor shall provide 24x7 hardware maintenance for the HQ AFWA Defense Meteorological Satellite Program (DMSP) Data Quality Monitor (DQM) system. The Contractor shall provide fault isolation and problem resolution. The Contractor shall recommend alternative courses of action to resolve problems. The Contractor’s recommendations are due no later than 3 days after problem identification. The Contractor shall replace items down to the Field Replaceable Level if provided by the Ground Systems Engineering and Depot Support (GSEDS) contractor. The Contractor will report status of actions taken to the System Duty Officer. (CDRL A001)

2.3.2.18 Reserved

2.3.2.19 Reserved

2.3.2.20 (ME) The Contractor shall provide 24x7 software sustainment for the PAIS.

2.3.2.21 Reserved

2.3.2.22 Reserved

2.3.3 (ME) For the Base Period, and Option Periods 1-3. The Contractor shall perform maintenance of software baselines identified in Table 1. The Contractor shall provide technical expertise in system analysis/programming in designing, developing, integrating, testing, and implementing incremental improvements to existing software and to maintain software to meet warfighter requirements. Maintenance includes identifying the source of processing problems and making corrections. The Contractor shall document its software development processes in the SDP. The Contractor shall perform software maintenance in according with its Software Development Plan (SDP). The Contractor shall create software design and maintenance documentation. The Contractor shall design, and develop/modify software programs including database programs in coordination with the Government. The Contractor shall submit change requests (SEMS III contract PWS para 2.1.8.1). The Contractor shall provide necessary artifacts to support the certification and accreditation process for software program changes. The Contractor shall provide technical expertise in integrating, testing, documenting (including test plans, procedures and reports), and implementing enhancements. The Contractor shall provide software/technical expertise to evaluate documentation and software. The Contractor shall identify problems and suggest improvements in design, coding, methods or procedures. The Contractor recommendations shall be summarized in a monthly report due 10 working days after the close of the previous month. Software to be integrated shall include but not be restricted to system, network and interface software. The Contractor shall document requirements and designs including data dictionaries. The Contractor shall provide the traceability of the Government’s requirements to functional, allocated and product baselines as appropriate including use cases. The Contractor shall prepare a software version description document for each new or revised software item. The Contractor shall document problems identified during testing and test results including certification of test results. The Contractor shall plan test activities. The Contractor shall deliver to the Government source and executable code developed and supporting documentation. (CDRL A001, A002, A003, A005, A006, A010, A011, A018, A024, A026, A027, A028, A035, A039, A042, A043, A044, A045, A047, A049)

OR

2.3.3 (ME) For Option Periods 4, 5 and the six month extension only. The Contractor shall perform maintenance of software baselines identified in Table 1. Maintenance includes identifying the source of processing problems and making corrections. The Contractor shall submit change requests (SEMS III contract PWS para 2.1.8.1). The Contractor shall prepare a software version description document for each revised software item. The Contractor shall document problems identified during testing and test results including certification of test results. The Contractor shall plan test activities. The Contractor shall deliver to the Government source and executable code developed and supporting documentation. (CDRL A003, A005, A006, A028, A039, A042, A044,)

2.3.4 (ME) TCNOs/Intelligence Community Vulnerability Alerts (ICVA) are considered mandatory directives. They are issued to ensure maximum protection of network/assets. The Contractor shall perform software maintenance activities necessary for TCNO/ICVA compliance unless directed otherwise by the Government. The Contractor shall document its TCNO/ICVA processes in the SDP. The Contractor shall perform software maintenance in accordance with the SDP. The Contractor is expected to define, develop, trouble-shoot, and resolve problems. Software maintenance shall include correction of system/network/interface software problems, database management functions, and installation of COTS and GOTS packages and system software revisions. The Contractor shall update technical documents as necessary. The Contractor shall perform system upgrades IAW AFCERTS, TCNO’s, ICVA’s, Directive C4 NOTAMs (Notice to Airmen), AFI33-138, and vendor requirements for all AFWA systems as identified in para 2.3.2 excluding software baselines under AFWA configuration control. All TCNOs, ICVAs and NOTAMS will be accomplished NLT the Air Force or Defense Intelligence Agency (as applicable) required due date as listed when issued to the Contractor by AFWA security personnel. For those that cannot be done by the required date, due to a mitigating measure is not available, or cannot be complied as directed in the order, the Contractor must provide a corrective action plan with milestones (i.e. POA&M) to the Government. This POA&M must be created within the designated tool and maintained by the Contractor, while oversight will be provided by the Government. If the Government does not provide sufficient time to test TCNOs, ICVAs and NOTAMS by the required due date, any impact to operational readiness due to TCNO, ICVA and NOTAM implementation will not be counted in the monthly calculation for operational readiness. The Contractor shall document its TCNO support processes in the SSP. The Contractor shall document all requirements and design changes due to TCNO/ICVA installation. (CDRL A002, A010, A011, A014, A018, A026, A035)

2.3.5 (ME) The Contractor’s sustainment activities shall include obtaining licenses and agreements. The Contractor shall document its license and support agreement acquisition and maintenance process in the ILSP. (CDRL A023)

2.3.5.1 (ME) The Contractor’s sustainment activities shall include obtaining the annual licensing and update services on third-party software, software drivers, and diagnostic software, necessary site licenses and any vendor support for all AFWA systems designated in para 2.3.2 including all non-applications software, and maintain the master record of these licenses and updates. It shall also include all hardware and software subscription services to maintain the COTS hardware and software at the latest vendor revision level. The Contractor shall deliver by the end of each fiscal quarter of each fiscal year a listing of and a rough order of magnitude cost estimate for each license and support agreement required for the next fiscal year and the most recent purchase price. The listing shall include the name, associated number designation if any, original manufacturer, numbers of licenses/support agreements, associated systems and renewal date for each license and support agreement. The Contractor shall not obtain licensing, update services, and vendor support without notifying the Government Contracting Officer in sufficient time to allow the Government to respond prior to the purchase. (CDRL A001)

2.3.5.2 (ME) The Government shall provide the funding through the contract for the Contractor to purchase the items in para 2.3.5.1. All changes considered mandatory by the computer system vendor shall be incorporated with approval of the Government. The Contractor shall use AF-wide license agreements whenever available. The Contractor shall assure all Contractor and tasked Government hardware and software meet current Air Force certification and accreditation requirements, Air Force Computer Emergency Response Team (AFCERT) requirements, and Defense Intelligence Agency certification and accreditation requirements.

2.3.6 (ME) The Contractor shall perform hardware maintenance to include all actions, parts, and equipment necessary for repairing or restoring to operations. The Contractor shall document its maintenance process in the ILSP for all task orders. The Contractor shall provide total maintenance to include, but not limited to, all inspections, diagnostics, preventive and corrective maintenance, cleaning, servicing, lubricating, replacing parts, troubleshooting, repairing, bench checking, reassembling, testing, calibrating, and conducting of operational checks to correct malfunctions and verify the adequate and proper serviceable condition of any component, system, or subsystem. The Contractor shall establish criteria to determine periodic maintenance requirements. The Contractor shall establish service agreements. To ensure operability of any replacement components, the Contractor shall perform system testing. All maintenance actions shall be IAW Government approved technical documentation. For equipment under manufacturer’s warranty, the Contractor shall place all maintenance calls to the hardware vendor, be the Government’s point of contact with the hardware vendor, and be responsible for all security while the maintenance vendor is performing maintenance actions. The Contractor shall prepare and process requests for the assignment, delegation, or revision of nomenclature for specified deliverable hardware on a system/subsystem level, and properly document nomenclature when approved. Requests are due within 30 days after nomenclature change identified. The Contractor shall provide provisioning data as needed for those spares to be stock listed. If parts are replaced with other than identical, then the Contractor shall update the appropriate drawings. The Contractor shall document all maintenance actions taken. (CDRL A001, A023, A032, A033)

2.3.7 (ME) The Contractor shall develop and maintain a material/supply chain management and tracking system to track all maintenance actions, and spares/repair parts. The Contractor shall document its material/supply chain management and tracking system in the ILSP for all task orders. The Contractor shall provide the records of this system upon expiration of the contract. Any item that currently is assigned a National Stock Number (NSN) shall be managed by the Government (Item Manager). The Contractor will be provided Military Standard Requisitioning Procedures authority. The Contractor shall establish an active program to continually monitor equipment and parts, to include COTS, to ensure availability. The Contractor shall be responsible for the replenishment, management, calibration, update, and maintenance of all Government furnished support equipment. The Contractor shall provide any additional resources, such as hand tools, not provided by the Government, necessary to accomplish these tasks. (CDRL A023, A032)

2.3.8 (ME) The Contractor shall perform system administration support for all AFWA systems as identified in para 2.3.2. The Contractor shall document its system administration support in the SSP for all task orders. The Contractor is responsible for systems on the Unclassified, Secret, and Top Secret SCI networks and the systems transferring data between Unclassified, Secret and SCI. The Contractor shall perform all COTS software and operating system installations, patches, maintenance, and performance tuning. The Contractor shall configure newly acquired information systems in accordance with applicable STIGs. The Contractor shall verify configuration by accomplishing appropriate security scan with the Security Readiness Review Scripts (SRRs) prior to implementation. The Contractor shall upload accomplished scan into the Vulnerability Management System (VMS), or other designated tool. The Contractor shall answer all identified vulnerabilities along with creating and maintaining POA&Ms against scanned assets within VMS, or other designated tool. Adjudication of answers will be provided by the Government. At a minimum, all systems must be scanned on a yearly basis and after each CCR implementation. The Contractor shall track privileged users for the systems they are responsible for and undergo an annual review with the Government.