Section_J _Attachment_20_-_SEMS_III_SWAFS_Sustainment_PWS_V1.2_29_Apr_13.docx

FA4600-12-R-0013-0001

Section J, Attachment 20

AIR FORCE WEATHER (AFW)

SYSTEMS ENGINEERING, MANAGEMENT AND SUSTAINMENT III (SEMS III)

SPACE WEATHER ANALYSIS AND FORECAST SYSTEM (SWAFS) SUSTAINMENT

PERFORMANCE WORK STATEMENT (PWS)

25 Oct 12

REVISION/CHANGE RECORD

1.0 DESCRIPTION OF SERVICES

1.1 PURPOSE

1.1.1 This Performance Work Statement (PWS) contains requirements for services and deliverables to perform Space Weather Analysis and Forecast System (SWAFS) sustainment activities.

1.2 SCOPE

1.2.1 The sustainment activities include Return to Service, Corrective Maintenance, Adaptive Maintenance, and addition of incremental capability improvements to the SWAFS operational software baseline.

1.3 BACKGROUND

SWAFS accepts space weather data and uses models and/or algorithms to create and disseminate specified space weather analysis and forecast products.

Development of SWAFS is addressed under separate efforts contracted through Space and Missile Systems Center/Defense Meteorological Satellite Squadron (SMC/DMSS), and is not addressed in this PWS.

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 shows the mapping of PWS 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 Reserved

2.2 Program Management/Systems Management

2.2.1 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 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 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 communicate status information and issues to the Government in a clear and timely manner. The Contractor shall maintain schedules in Microsoft® Project. (CDRL A001, A007, 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 including software pseudo-function point count, metrics for software baseline management, program issues, status of corrective actions, and upcoming events summary. The Contractor shall brief the monthly status report to Government program management/contracting officer’s representative personnel, and the Air Force Weather Agency (AFWA) Commander. The financial portion of the monthly status report shall be briefed at a separate meeting. (CDRL A009, A031)

2.2.3 Reserved

2.2.4 The Contractor shall develop and maintain the Data Management processes. This includes recommending actions that minimize the cost of data to the Government while maintaining baseline integrity.

2.2.4.1 Management Information System (MIS)

The Contractor shall maintain technical documentation required to support this task order. 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 task order 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. 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.

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.

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 Reserved

2.2.5.1 Reserved

2.2.5.2 Reserved

2.2.5.3 Reserved

2.2.5.4 Reserved

2.2.5.5 Reserved

2.2.6 The Contractor shall provide risk assessments and employ risk management processes in accordance with the SEMS III 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 contract PWS 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 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 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. (CDRL A001, A009)

2.3 Systems Sustainment

2.3.1 The Contractor’s sustainment focus shall be to maintain AFWA systems to meet required operational readiness rates while lowering ownership costs in accordance with the Systems Sustainment Plan and the Integrated Logistics Support Plan. 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. In performing software maintenance, the Contractor shall perform design, 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. The Contractor shall perform analysis in response to system questions in accordance with SEMS III contract PWS para 2.1.11. 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) 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 A037, A050, A054)

2.3.2 (ME) The Contractor shall maintain the SWAFS software baseline as specified in the following subsection (summarized in Table 1) and in accordance with the Systems Sustainment Plan. The Contractor shall ensure the system capability of all specified 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). (CDRL A039)

Table 1 Sustainment Requirements

Table 2 (Reserved)

2.3.2.1 Reserved

2.3.2.2 Reserved

2.3.2.3 Reserved

2.3.2.4 Reserved

2.3.2.5 Reserved

2.3.2.6 Reserved

2.3.2.7 Reserved

2.3.2.8 Reserved

2.3.2.9 Reserved

2.3.2.10 Reserved

2.3.2.11 Reserved

2.3.2.12 Reserved

2.3.2.13 Reserved

2.3.2.14 Reserved

2.3.2.15 Reserved

2.3.2.16 Reserved

2.3.2.17 Reserved

2.3.2.18 (ME) The Contractor shall provide 24x7 software sustainment for the HQ AFWA Space Weather Analysis and Forecast System (SWAFS). Software sustainment includes emergency on-site maintenance, correcting deficiencies and making minor enhancements to maintain the SWAFS operational software baseline. The major software sustainment releases shall be designated as sustainment bundles. Minor software sustainment releases shall be designated as patches. The Contractor shall perform Level 1 and Level 2 corrective sustainment to prevent performance degradation and prevent or correct system failures to ensure SWAFS software continue to operate and meet mission requirements. Level 1 sustainment is minor modifications that do not require changes to compiled source code and designated scripts. Level 2 sustainment is a major modification that request change to compiled source code and designated scripts. The Contractor shall correct code design faults in the operational software baseline. The Contractor shall provide adaptive software changes to retain compatibility with AFWA enterprise architecture changes as they impact the SWAFS operational software baseline. The Contractor shall provide adaptive software and database schema changes necessary to ingest and database space weather data from new satellite and ground-based sensors, to accommodate new space weather models, algorithms, and indexes delivered as part of the SWAFS development effort, and to implement requirements to support evolving operational capability needs for military forces in multiple theaters of operation worldwide. Operator orientations shall be provided for the capabilities provided in the new block releases. Work performed in accordance with this PWS shall consider SWAFS development activities managed jointly by the Defense Weather Systems Directorate at the Space and Missiles Systems Center, and AFWA/A8P and separate sustainment tasks as managed by AFWA/A8P in block release content planning. Block releases may be combined with separate software sustainment or development activities and integrated as a single baseline delivery to reduce delivery costs. All enhancement requirements shall be identified by the Government. The Contractor shall provide scientific and technical analysis of space weather physics and space weather research results as specified in task orders for consideration in future releases. The Contractor shall provide recommendations on how to improve and integrate new, and sustain existing, space weather models, algorithms and indexes used in AFWA’s space weather program and products. The Contractor shall brief the design for each block release. The Contractor shall document software changes in a version description document for each block release. The Contractor shall update user manuals as necessary to maintain them current with the release. The Contractor shall provide necessary information assurance documentation to the Government. (CDRL A001, A003, A018, A024, A025, A026, A027, A035, A036, A039)

2.3.2.19 Reserved

2.3.2.20 Reserved

2.3.2.21 Reserved

2.3.2.22 Reserved

2.3.2.23 Reserved

2.3.3 (ME) The Contractor shall perform maintenance of the software baseline 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 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. 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)

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 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 SWAFS software baseline. 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, A018, A026, A035)

2.3.5 Reserved

2.3.5.1 Reserved

2.3.5.2 Reserved

2.3.6 Reserved

2.3.7 Reserved

2.3.8 Reserved

2.3.9 Reserved

2.3.10 Reserved

2.3.11 Reserved

2.3.12 Reserved

2.3.13 Reserved

2.4 Reserved

2.5 Other Direct Costs and Travel

2.5.1 All materials, equipment, software, and documentation purchased by the Contractor for the use or ownership of the Government, becomes the property of the Government at the end of the contract. The Contractor shall document the transfer of these items. There will be no profit or fee allowed on other direct costs.

2.5.2 The Government may require the Contractor to attend TIMs held at locations other than HQ AFWA in support of this contract. The Government will reimburse the Contractor for travel expenses incurred in direct support of the required meeting including lodging, transportation (airfare, personal/rental vehicle), and per diem. Fees will not be applied to travel costs under this contract. All travel requirements must be authorized and funded in advance by the Contracting Officer. The Contractor shall submit an itinerary of the planned trip to the Government’s Contracting Officer Representatives (CORs) for approval no later than five (5) working days in advance of departing for the trip. NOTE: Approval of the itinerary by the Contracting Officer does not imply acceptance or reasonableness of the estimated travel costs. Travel costs will be reimbursed IAW the Federal Acquisition Regulation (FAR) 31.205-46 and the Joint Travel Regulation. There will be no profit or fee allowed on travel costs.

2.5.3 Official Government or Contractor mail that is generated as a result of performance of this contract shall be handled via the Base Information Transfer System (BITS) at Government expense. BITS may not handle non-Government mail to or from the Contractor.

2.5.4 The Contractor shall be responsible for all packaging and shipping of materials IAW best commercial practices to meet the packing requirements of the carrier and timely delivery at the intended destination. The Contractor shall ship all items for repairs as necessary.

2.6 All data deliverables and reports shall be in accordance with instructions in this task order. Deliverable schedules shall be in accordance with instructions in this task order. The Contractor shall deliver the services, and deliverables(Table 3, paragraph 2.9) specified in this PWS.

2.7 Reserved

2.8 Contractor Performance Evaluation

The Government will evaluate the Contractor’s performance under this contract. The Incentive Fee Plan and the Services Summary will specify the criteria of evaluation. In addition, Contractor performance shall be evaluated using the Contractor developed, Government approved, system performance measurement process (para 2.2.7). Government personnel will record all surveillance observations. Surveillance will be done according to standard inspection procedures or other contract provisions.

2.9 Contract Data Requirements List (CDRL)

Table 3 Deliverables

15 Workdays After End of Contractor Accounting Month Contractor Format

3.0 SERVICES SUMMARY

The Government will use appropriate Services Summary items below (Table 4) to evaluate the Contractor’s performance for each task order separately. Services Summary table in individual task order Performance Work Statements (PWS) will indicate which Services Summary items the Government will use for that task order. The type of task order determines which Services Summary items the Government will use.

Table 4 Services Summary

100% without failures

100% submitted before or on due date

1 Reference TO 00-35D-54, Table 1-2 2 “Actively used” means that the Contractor reviews risk mitigation steps monthly and reschedules dates that are past due or completes each step before its due date.

Operational Readiness*

PO-17 Software sustainment for HQ AFWA SWAFS

PO-19 On-call response

For “duty hour”** support, greater than 95% of duty hours on-call requests are responded to within 20 minutes of original call. When on-call support personnel are offsite during duty hours greater than 95% of on-site arrivals are within 60 minutes of determination that on-site support is required.

For “best effort” support, on-call requests are responded to as resources become available during duty hours.

*NOTE: Operational readiness is the probability that the system is operating satisfactorily at any point in time excluding scheduled maintenance and training. (Air Force Technical Order 00-33A-1001, para 13.2.2.1.1.b, page 13-1)

**NOTE: Duty Hours are 0730-1630 Mon-Fri excluding Federal Holidays.

4.0 GOVERNMENT-FURNISHED PROPERTY AND SERVICES

4.1 Government-Furnished Property and Facilities

4.1.1 All personnel employed by the Contractor in the performance of this contract, or any representative of the Contractor entering Offutt AFB, shall abide by all security regulations of Offutt AFB and AFWA. The Contractor shall coordinate with the designated AFWA representative for Government-furnished ADT® cards and Common Access Cards.

4.1.2 The Contractor is entrusted with ADT® cards for facility access and shall prohibit the use of Government-issued access devices by any person other than authorized Contractor employees. The Contractor shall not permit entrance to locked areas by any person other than Contractor personnel assigned to the activity where the Contractor is performing work, without written authorization by the Government’s CORs. Access devices shall only be issued to Contractor employees performing services under this Contract. The Contractor shall immediately report to the Government’s CORs any occurrences of lost access devices.

4.1.3 The Contractor shall operate Government-provided computer equipment in accordance with AFI 33-200 Information Assurance Management. The Contractor shall attend Government provided computer training prior to accessing data on the Government’s network.

4.1.4 Reserved

4.1.5 Reserved

4.1.6 Reserved

4.1.7 The Government will furnish or make available to the Contractor facilities in AFWA. The facilities will be jointly occupied with the Government or other Contractors. The Contractor shall maintain all furnished facility space in a neat, clean, orderly, and sanitary condition. Government-furnished facilities shall be kept free from accumulations of waste material and/or debris at all times. Contractor alterations or improvements to assigned facilities shall be provided at the Contractor’s expense. The Contractor shall not make any alterations or improvements to the facilities except with advanced written permission from the Government’s CORs and prior approval of the AFWA Facility Manager. Any such alterations or improvements become the property of the Government; however, if the Government requires removal or dismantling of such improvements, it shall be accomplished at the Contractor’s expense. The Government reserves the right for no-notice visits to Contractor work areas for the purpose of inspecting conditions or activities for hazards or investigate safety complaints or incidents. All areas shall be subject to fire, safety, and health inspections at any time by Government personnel. The Contractor shall be responsible for correcting any cited violation within two (2) working days.

4.1.8 The Contractor shall provide all personnel, equipment, and materials necessary to perform the relocation of any equipment within HQ AFWA. The Government reserves the right to reallocate or redistribute the Contractor’s Government-provided office space. If the Government reallocates or redistributes the office space, the Contractor shall provide all personnel, equipment, and materials necessary to relocate all Government and Contractor provided office equipment, furniture, and supplies. The Contractor shall be responsible for the security of equipment during relocation.

4.1.9 Utilities for Government-furnished facilities will be provided at no cost to the Contractor. Utilities are limited to electricity, water, sewage, and telephone. The Government will provide a Personal Identification Number for use on all long distance calls in support of the requirements of this contract.

4.1.10 Reserved

4.1.11 The Contractor shall receive Operational Security (OPSEC) training from the Government. The Contractor shall report via Government specified method training completed. The Contractor shall review AFWA’s Critical Information List (CIL). The Contractor shall report the costs incurred to satisfy this paragraph's requirements in the Contract Performance Report. The Contractor shall protect critical unclassified information used outside of DoD information systems IAW DoDI 8582.01. (CDRL A007)

4.2 Safety of Government Property and Facilities

4.2.1 The Contractor shall safeguard all Government property in its work area. At the close of each work period, facilities shall be secured.

4.2.2 The Government will provide fire protection services on base. The Contractor shall comply with NFPA 1, Fire Prevention Code and AFOSH 91-56, Fire Protection and Prevention. The Government will make available to the Contractor restricted LAN connectivity and systems and maintenance thereof. Custodial service will be provided for the facilities to the extent provided by the custodial Contractor.

4.2.3 All Government-furnished facilities have been inspected for compliance with the OSHA. No hazards have been identified which required the establishment of work-arounds. Should subsequent hazards be identified, the Government will correct them according to base-wide Government developed and approved plans of abatement which take into account health and safety priorities. The fact that no such conditions have been identified does not warrant or guarantee that no possible hazard exists, or that work-around procedures will not be necessary or that the facilities as furnished will be adequate to meet the responsibilities of the Contractor. Compliance with the OSHA and other applicable laws and regulations for the protection of employees is exclusively the obligation of the Contractor. Furthermore, the Government will assume no liability or responsibility for the Contractor’s compliance or noncompliance with such requirements, with the exception of the aforementioned requirement to make corrections according to approved plans of abatement subject to base-wide priorities.

4.3 The Contractor shall provide quality assurance processes that ensure all Contract requirements shall be satisfied.

4.4 The Contractor’s normal hours of operation shall be 0730 to 1630, Monday through Friday, excluding federal holidays. The Government retains the right to change normal working hours at any time.

4.4.1 The Contractor shall meet unscheduled mission or emergency requirements on a 24-hour basis, 365 days a year. The after normal hour requirements are in para 2.3.2.

4.4.2 Contractor personnel deemed non-essential for current on-site operations by the Government’s CORs may be released during duty hours upon notification by the applicable base authority of a severe weather contingency or other emergency requiring release of Government personnel from duty at Offutt AFB.

4.5 The Contractor shall perform the services described herein primarily at the HQ AFWA location in the Lt. General Thomas S. Moorman Building (Bldg 185) on Offutt AFB NE and adjoining areas on Offutt AFB, and the 14th Weather Squadron, 151 Patton Ave Room 120, Asheville, NC. Occasionally, the Contractor shall perform services at other Air Force Weather locations. The Government will provide travel reimbursement on a case by case basis.

4.6 The Contractor shall provide surge support for requirements in this PWS as determined by Government priority and tasking. Surge support is defined as short-term support (a few weeks duration) above normal operational levels necessary to address high priority immediate needs. Additional funding will be provided by the Government to cover surge activities.

4.7 The Contractor shall establish relationships with Contractor partners to provide contingency support for infrequent situations requiring expert assistance to resolve AFWA applications, network, or system problems beyond normal support requirements identified in this PWS. Contingency support may be necessary during other than duty hours. Additional funding will be provided by the Government to cover contingency activities.

ATTACHMENT 1

Reference Documents List

This list may be found in the SEMS III Contract PWS, Attachment 1.

ATTACHMENT 2

PWS-CLIN Mapping

2.2.1

2.2.2

2.2.4

2.2.6

2.2.7

2.3.1

2.3.2

2.3.2.18

2.3.3

2.3.4

2.5

4.1.11

4.3

ATTACHMENT 3

Unfunded Requirements

Reserved

ATTACHMENT 4

Government Requirements

ATTACHMENT 5

Addendum to SEMS III Incentive Fee Plan (IFP)

ATTACHMENT 6

Sustainment Model

SEMS III Space Weather Analysis and Forecast System Sustainment PWS V1.2