Section_J _Attachment_21_-_Advanced_Meteorological_Model_Development_Project_PWS_25_Sep_13.docx

FA4600-12-R-0013-0003

Section J, Attachment 21

AIR FORCE WEATHER (AFW)

SYSTEMS ENGINEERING, MANAGEMENT AND SUSTAINMENT III (SEMS III)

ADVANCED METEOROLOGICAL MODEL DEVELOPMENT PROJECT

PERFORMANCE WORK STATEMENT (PWS)

13 Sep 12

REVISION/CHANGE RECORD

1.0 DESCRIPTION OF SERVICES

1.1 PURPOSE

This PWS contains the contract requirements to take meteorological model research software and produce a version for mission operations. The tasks include management, engineering (system and software), and documentation (design products).

1.2 SCOPE

This PWS specifies all contract requirements necessary to deliver a software modification to meteorological models.

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 Systems Engineering

2.1.1 The Contractor shall perform design, development, integration and test, and provide implementation analysis for modifying a research model to a version that can be placed in operations. This project will rewrite a portion of the model to make it able to be used in operations and able to perform software maintenance. Attachment 4 provides the Government requirements for this task order. To perform this task order, the Contractor shall implement a system engineering process in accordance with the Systems Engineering Management Plan (SEMP). The Contractor shall implement software development processes for software development, software modification unit test, implementation and installation in accordance with the Software Development Plan (SDP). 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 prepare and deliver a Project Plan/Requirements Review. This document shall specify the proposed tasks and task’s schedule the Contractor shall accomplish to successfully meet task order requirements. Also, in the document, the Contractor shall present the Contractor’s understanding of the Government’s requirements. The Contractor shall describe in the Project Plan/Requirements Review how its processes shall attain the appropriate objective threshold values contained in the Services Summary. (CDRL A051)

2.1.2 The Contractor shall conduct a design review. The Contractor shall provide and maintain the traceability of the Government’s requirements to functional, allocated and product baselines including use cases, system requirements, software requirements, design, and levels of testing and code. The Contractor shall provide recommendations on development, integration requirements, hardware requirements, schedule requirements, operations and maintenance concepts. The Contractor shall present site preparation requirements, lifecycle cost estimates, information security, dependencies with existing systems/applications, required existing applications modifications, and technical impacts of design, development, test, and implementation/integration. The items required in paragraph 2.1.3 shall be addressed in the design review. The Contractor shall document the design review events and significant proceedings including action items. The Contractor shall ensure that use of the Enterprise Storage Solution (ESS), Data Pipe, Anti-Virus Management System, and Tivoli are considered on this modification. The Contractor shall consider existing software and tools in use for sustainment before recommending new software and tools. (CDRL A001, A017, A024, A045)

2.1.3 The Contractor shall participate in Technical Interchange Meetings (TIMs). The TIM exchanges information on operational and performance characteristics, both technical and functional, with various Government offices and other Government contractors. The Contractor shall participate in TIMs to discuss and resolve interface issues development issues, integration issues, test issues, implementation issues, information security issues, schedule issues, performance issues, safety issues including hazards that cannot be eliminated, and sustainment issues. At TIMs, the Contractor shall provide briefings on proposed system changes. (CDRL A038)

2.1.4 The Contractor shall perform system design and implement proposed system designs for modifications. The Contractor shall define and record the software requirements to be met by each Configuration Item (CI) and COTS item, the methods to be used to ensure each requirement has been met, and the traceability between CI requirements and allocated system requirements. The Contractor shall document any changes to interfaces in accordance with paragraph 2.1.8.1. The Contractor will make the software CI requirements accessible by the Government with existing Government tools. The Contractor shall define and document the software architectural design of each CI, including interfaces and concept of execution among the CIs. The Contractor shall develop and document a description of each software unit in accordance with industry accepted software development standards meeting Capability Maturity Model Integration® – Development Level 4, V1.2 including data dictionaries. The Contractor shall perform software code review IAW Defense Information Systems Agency (DISA) application Security Technical Implementation Guides (STIG) and the SEMP/SDP. The Contractor shall develop and document unit and integration test plans and procedures for each software unit. The Contractor shall integrate tested software units and test the resulting software integration according to the test plan. The Contractor shall revise software units as needed to correct defects discovered during software integration. The Contractor shall document the code and test results for Government review. The test results shall demonstrate to the Government that CI requirements have been met. The Contractor shall prepare a software version description document for each new or revised CI. The Contractor shall acquire hardware, firmware, and software information security components that have been evaluated and validated prior to acquisition, using criteria and processes established by the Government. The Contractor shall deliver to the Government source and executable code developed and supporting documentation. (CDRL, A002, A003, A005, A006, A010, A018, A026, A028, A035, A039)

2.1.5 The Contractor shall conduct acceptance test. The Contractor shall plan with the Government and support (be present at, provide necessary software modifications for, provide systems administration services for) operational evaluations. The Contractor shall develop test plans and procedures to conduct system level acceptance testing, to verify allocated requirements and to verify interface integrity. The Contractor, with the Government, shall develop operational evaluation test plans and test procedures. The Contractor shall ensure tests will not adversely affect current operations. The Contractor shall verify the adequacy of the test equipment, staff, and schedule and shall assess the adequacy of operational scenarios when evaluating the test plans and its ability to verify that all capability needs are met. The Contractor shall develop test plans that verify the relationship among mission needs, mission environments, system requirements and test criteria. The Contractor shall provide recommendations to mitigate any inadequacies in the test plans. The Contractor shall oversee system level testing for modified and delivered systems to ensure operability and compatibility with other subsystems. This shall include: on-system testing of any newly developed/purchased Government furnished property software, verification of system performance, support for the Government’s security testing and evaluation, and recommending alternatives to optimize system performance. The Contractor shall conduct acceptance test readiness reviews and acceptance test result reviews. At test readiness reviews, the Contractor shall present the test plan/procedures including test equipment, staff, schedule, requirements to be verified, problem reports to be addressed, and known risks if any. At test result reviews, the Contractor shall present any changes to test equipment, staff, schedule, requirements verification and problem reports. The Contractor shall document the test results in a test report including certification of test results which shall include test equipment, schedule, test plans, test procedures, any variations from the test procedures and the problem reports. (CDRL, A005, A006, A028, A042, A043, A044)

2.1.6 Reserved

2.1.7 The Contractor shall assure System Security Engineering (SSE) is integrated into project tasks. All aspects of SSE are to be considered (i.e., physical, personnel, computer, communications, and emissions). For systems identified in SEMS III Contract paragraph 2.3.2, the Contractor shall analyze system architectures, assist in conducting tests required to fulfill the Government’s C&A requirements, and support the development and updates to the DIACAP/ICD 503 packages. This support shall be in the form of providing design artifacts, support documentation, or ports and protocol information to the Government. The Contractor shall assist in the development of C&A documentation for modification by providing the Government the supporting information and documentation artifacts. The Contractor shall provide a description 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 assist the Government in verifying hardware and software components are identified in Department of Defense Information Assurance Certification and Accreditation Process (DIACAP)/ICD 503 documents when submitted for certification approval. The Contractor shall assist the Government with the Cross Domain Solution process, DISN Security Accreditation Working Group (DSAWG) and the Cross Domain Management Office (CDMO) by providing supporting design details accordingly. The Contractor shall identify associated project deliverables, milestones, and timeliness requirements to the Government to assist in tracking C&A documentation through the approval processes. The Contractor shall follow the Configuration Change Request process and ensure any and all changes are approved by the Configuration Change Board in accordance with paragraph 2.1.8 below. The Contractor shall keep current Remedy (or other designated tool) with hardware, software, (including what software is installed on each box), IPs and hostnames. The Contractor shall utilize Remedy (or other designated tool) to keep current the status of Time Compliance Network Orders (TCNO). In addition, for those that cannot be done by the required date, a Plan of Action and Milestones (POA&M) must be created, kept updated and provided to the Government. This POA&M must be created within designated tool and maintained by the Contractor, while oversight will be provided by the Government. 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. (CDRL A027, A050)

2.1.8 The Contractor shall develop, implement, and maintain the Configuration Management (CM) process for developed and sustained CIs in accordance with the Configuration Management Plan. CM processes shall be capable of controlling multiple baselines and tools, and absorbing other baselines. The CM Plan shall also address how all recompetition data (e.g. test, logistics, software, engineering, configuration, security, and requirements) shall be managed and the method for making recompetition data available to the Government and follow-on bidders. To the maximum extent possible, CM data shall be easily and electronically accessible to the Government in native format to enable manipulation for future Government use and to provide current data on configuration change activities within the system. Government access must be either by Contractor provided tools or tools currently in use by the Government. To the maximum extent possible, the Contractor shall use existing Government tools in use. If the Contractor selects tools other than existing Government tools, then the Contractor’s tools shall be compatible with the Government tools such that the Government tools can receive and process output from the Contractor tools. The Contractor shall develop and maintain a CSA system. The CSA system shall adequately define, capture, store, and provide access to all configuration information needed to manage the assigned Air Force Weather (AFW) system project configuration baselines and provide end-to-end traceability. The Contractor shall ensure that all data (including version descriptions documents and COTS manuals) supported under this PWS are maintained to the current life cycle phase configuration. Maintenance of the documents supported under this PWS includes, but is not limited to, updates, corrections or integration of existing formats or contents of this documentation subject to Government approval. The Contractor shall adhere to documented Government processes, in submitting baseline and process changes to the Government for approval. The Contractor shall maintain configuration control of assigned enterprise functional, allocated and product baselines. (CDRL A003, A041)

2.1.8.1 The Contractor shall prepare change requests (CRs) and appropriate documentation changes to describe the scope and impact to include estimates of a modification and upgrade or any change to configuration baselines. The CR, or accompanying documentation, will address changes to all system and software documentation, including but not limited to, specifications, drawings including 3-dimensional floor layout and assembly drawings, technical manuals, and training requirements. The Contractor shall describe changes to existing equipment and spares and describe the required new equipment. (CDRL A002, A005, A006, A010, A018, A024, A025, A026, A028, A031, A033, A041, A047, A050)

2.1.8.2 The Contractor shall establish or bring to current a system performance baseline for each system modified, updated or maintained. The system performance baseline will consist of requirements, standards, system configuration, component specific configuration/setup instructions, system and software documentation, software media, costs, facilities/equipment/property, and maintenance requirements as applicable, training, information security, remaining work, and risks. The Contractor shall configure newly acquired information systems in accordance with applicable STIGs and provide the results to the Government. 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. (CDRL A016, A027)

2.1.8.3 Reserved

2.1.9 The Contractor shall ensure that procedures described for the operations of equipment are consistent with the safety standards established by the Occupational Safety and Health Administration (OSHA) and with the safety requirements of Air Force Occupational Safety and Health (AFOSH). These standards are to be referenced in all Contractor developed and maintained technical publications. The Contractor shall implement a management and engineering process to ensure that all system safety, operational safety, and chemical, physical, radiological and biological health hazards are identified and eliminated, reduced, or controlled within the constraints of project cost, schedule, and performance. The Contractor shall document all hazards that cannot be eliminated. (CDRL A001, A025)

2.1.10 Reserved

2.1.11 Reserved

2.1.12 Reserved

2.1.13 The Contractor shall provide responses to Government inquires of baseline descriptions under SEMS III control. Such exchanges are intended to facilitate development of optimal system level requirements, roadmaps, system architectures, capability integration plans, and performance work statements. These responses will be used by the Government to understand existing design constraints, limiting factors, and historical design/engineering approaches. (CDRL A001)

2.1.14 Reserved

2.1.15 Reserved

2.2 Program Management/Systems Management

2.2.1 The Contractor shall conduct all program management/system management activities for this contract 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 this task order’s requirements in accordance with the PM/SM Plan. Personnel shall possess necessary professional certifications commensurate with tasks assigned. The Contractor shall continually monitor cost, schedule including key milestones, and performance under this task order 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 this task order 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 this task order. The Contractor shall modify as necessary, implement, and maintain the Government provided CWBS that clearly defines how this task order 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, and program management activities for this task order. 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, metrics for software baseline management, program issues, status of corrective actions, QA nonconformance resolution, and upcoming events summary. 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 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 contract. 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.6 The Contractor shall assess this task order and provide risk assessments in accordance with the PM/SM Plan. The Contractor shall identify risks and develop risk mitigation strategies to ensure this task order has 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. 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, and recommend system performance metrics. The Contractor shall use well defined, outcome-based, metrics for metrics collection and analysis. 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. 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 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 Air Force Weather Agency (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. 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. 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

30 calendar days after request (paragraph 2.1.3) No later than 3 workdays of identification (paragraph 2.2.1, 4.1.5 and 4.1.10) Contractor Format

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% submitted before or on due date

Cumulative to date Cost Performance Index (CPI) Evaluated once per month using the Contract Performance Report. Outside of threshold no more than 25% of period of performance.

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.

Schedule

Reference timelines are based on project Contract Award (CA).

Project SCHEDULE

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 Reserved

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 The Contractor shall immediately report lost, stolen, damaged, or destroyed Government property, maintained in the Contractor’s property management system as identified in the SEMS III Contract PWS paragraph 4.1.4, to the Government’s CORs. A Report of Loss shall be prepared by the Contractor and forwarded to the Government’s CORs along with written explanation. The Contractor shall participate in the survey investigation. (CDRL A001)

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.1.12 The Government will be responsible for consumable items such as writing paper, copier/printer supplies, pencils, pen, etc. for personnel at AFWA’s facility (Building 185) on Offutt AFB, NE.

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. The processes shall show how validated customer complaints are processed and feedback provided.

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 paragraph 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 AFW 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.1.1

2.1.2

2.1.3

2.1.4

2.1.5

2.1.7

2.1.8

2.1.9

2.1.13

2.2.1

2.2.2

2.2.4

2.2.6

2.2.7

2.5

4.1.11

4.3

ATTACHMENT 3

Unfunded Requirements

Reserved

ATTACHMENT 4

Government Requirements

1. The research software shall provide precipitation analysis or cloud forecast products.

2. The research software shall be provided by the Government to the Contractor.

3. The research software shall be written using a commercial version of the FORTRAN language.

4. The research software shall consist of approximately 20,000 software lines of FORTRAN code.

5. Approximately 10,000 software lines of research software code shall be rewritten to increase execution speed and to be used in mission production.

6. The research software including the new lines of code must be documented to facilitate software maintenance and incremental improvements.

ATTACHMENT 5

Addendum to SEMS III Incentive Fee Plan (IFP)

This attachment is an addendum modifying the SEMS III IFP for the Advanced Meteorological Model Development Project task order. The items below are changes to the SEMS III IFP for this task order.

1. The Advanced Meteorological Model Development Project task order is a Type A task order as defined in the SEMS III IFP.

2. SEMS III IFP para 2.1.7 is modified for this task order to read as follows: Performance Objective #7 (PO-7): The Government project manager will verify in the Contractor’s contract performance report that the cost efficiency (Cost Performance Index (CPI)) for cumulative to date is no less than 1.00 and no greater than 1.10. The Government project manager will perform this verification once per month during the Project task order period of performance. The Contractor’s cost efficiency may be outside of threshold for no more than 25% of the period of performance. If cost efficiency for cumulative to date is less than 1.00 or greater than 1.10 for more than 25% of the period of performance, then no points will be granted for this area.

ATTACHMENT 6

Sustainment Model

Reserved

SEMS III Advanced Meteorological Model Development Project PWS V1.1