Section_J _Attachment_1_-_SEMS_III_Contract_PWS_V1.4.docx

FA4600-12-R-0013

Section J, Attachment 1

AIR FORCE WEATHER (AFW)

SYSTEMS ENGINEERING, MANAGEMENT AND SUSTAINMENT III (SEMS III)

CONTRACT

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, development 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 engineering, program management/systems management, and systems sustainment 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 design, development and delivery of efficient and reliable systems to reduce ownership costs while improving system performance, combined with strong and up-to-date knowledge of technology solutions are key components of this service. Additionally, 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 lists the reference documents for Government policies and procedures. The documents identified in Atch 1 are for reference only. This PWS and task order PWSs 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.

1.2.2 The requirements identified within this PWS are described in general terms. Each task order shall specifically address task requirements, project schedules, and other related performance criteria.

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). 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. Detailed procedures and checklists, referenced but not provided in the SEMP, shall be available to the government via the data accession list (DAL). These procedures and checklists provided on the DAL shall be available to the government to coincide with the activities being performed by the contractor. These software development processes shall reflect processes that meet or exceed Capability Maturity Model Integration®-Development maturity level 4. The specific version (e.g., V1.2 or V1.3) required will be as specified in task orders. 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. As specified by task order, 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 task order 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 A013, A029, A049, A051)

2.1.2 The Contractor shall conduct system level design reviews when required in support of task orders. The Contractor shall document design processes including cost estimation processes in the SEMP and the SDP as appropriate. The Contractor shall provide and maintain the traceability of the Government’s requirements to functional, allocated and product baselines as appropriate including use cases, system requirements, software requirements, design, and levels of testing and code. The Contractor shall provide recommendations on development, integration requirements, schedule requirements, operations and maintenance concepts, plans and procedures. The Contractor shall present system planning, site preparation requirements, system transition plan if applicable, 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 consider human systems integration requirements in the design to include manpower, personnel, training, and human factors to address human capabilities and limitations. 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 all modifications as specified by task orders. The Contractor shall consider existing software and tools in use for sustainment before recommending new software and tools. (CDRL A001, A017, A022, A024, A045)

2.1.3 The Contractor shall attend technical reviews. The technical reviews and meetings will serve to establish, review and verify functional and performance requirements. The Contractor shall provide reviews, comments, technical evaluations, as required. 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 as necessary. (CDRL A001, A038)

2.1.4 The Contractor shall perform system designs and implement proposed system designs for modifications and/or new capabilities as specified by task orders. The Contractor shall describe system and software development and implementation processes in the SEMP and SDP as appropriate. 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 including data dictionaries. The specific version (e.g., V1.2 or V1.3) required will be as specified in task orders. The Contractor shall perform software code review IAW Defense Information Systems Agency (DISA) application Security Technical Implementation Guides (STIG) and the SEMP/SDP processes. 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. The Contractor shall deliver operator training, operator procedures, and training documentation to include CI maintenance. (CDRL A002, A003, A005, A006, A010, A018, A026, A028, A035, A036, A039, A055)

2.1.5 The Contractor shall conduct acceptance test as specified by task orders. The Contractor shall document test processes in the SEMP and SDP as appropriate. 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, as required, 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 ensure that robust testing is performed including off nominal testing. This testing includes, but is not limited to: documenting the range of input and output parameters and test at the limits and beyond (Extreme Value Testing) except for case-by-case items as approved by the Government; and documenting, approving (sign-off), and making available for inspection and audit, unit level testing that affects systems and software requirements (e.g. timeliness, accuracy). 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 hardware and software, verification of system performance, support for Government 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 including certification of test results in a test report which shall include test equipment, schedule, test plans, test procedures, any variations from the test procedures and the problem reports. When requirements/functions are verified during development instead of at Government test, they shall be indicated in the System Test Procedures, and the records of these verification activities provided to the Government as a part of the System/Software Test Report. (CDRL, A005, A006, A028, A042, A043, A044)

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 assure System Security Engineering (SSE) is integrated into all task orders. The Contractor shall describe SSE processes in the SEMP. All aspects of SSE are to be considered (i.e., physical, personnel, computer, communications, and emissions). For systems identified in paragraph 2.3.2, the Contractor shall analyze system architectures, assist in conducting tests required to fulfill Government 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 a specific acquisition, modification, or upgrade 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 (CCR) process and ensure any and all changes are approved by the Configuration Change Board in accordance with para 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 as specified by task orders. These CM processes shall be captured in the CM Plan (or SEMP/SDP as applicable) that includes configuration control, configuration status accounting (CSA), configuration verification and audit, and configuration identification for all systems and software CIs. 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 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, A015, A041)

2.1.8.1 The Contractor shall prepare change requests (CR) and appropriate documentation changes to describe the scope and impact to include development and sustainment 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 A001, A002, A005, A006, A010, A011, A018, A024, A025, A026, A028, A031, A033, A035, A041, A047, A050, A052, A053)

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, transition to operations plan, training, information security, remaining work, and risks. The Contractor shall configure newly acquired information systems in accordance with applicable STIGs and provide 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 The Contractor shall perform functional, physical, and facility configuration audits in conjunction with the Government as specified in task orders, and apply follow up processes to ensure audit discrepancies are addressed. The Contractor shall document all audit discrepancies. For the physical configuration audit, the Contractor shall prepare a list of the installed hardware and software using existing documentation that identifies the following:

a. Hardware item and quantity, manufacturer/vendor's name, part number and serial number.

b. Software vendor's or developer’s name, software nomenclature, version number and date released.

c. Software license requirement(s).

d. List of Item Unique Identifiers (IUIDs) to include a description of the equipment. (CDRL A001)

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 process shall be documented in the SEMP. The Contractor shall document all hazards that cannot be eliminated. (CDRL A001, A011, A013, A025)

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 Contractor shall conduct and deliver to the Government an annual assessment of the adequacy of existing power in all enclaves. (CDRL A001)

2.1.11 As specified by task order, the Contractor shall apply the systems engineering process to identify, investigate, and analyze candidate operational concepts and technology enhancements and assess their applicability to AFW. The Contractor shall technically evaluate and recommend the feasibility of implementing new technologies. The Contractor shall evaluate Government proposed system life extension and performance enhancement programs as necessary; 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 recommend value-added engineering changes to reduce the cost of ownership. The Contractor shall assess communications bandwidth adequacy and future bandwidth requirements. The products of engineering analysis may be design solutions, impact assessments, cost estimates, engineering analysis, technical and cost tradeoffs, development and sustainment requirements identification, the results of feasibility studies with alternate solutions, operational evaluation software and hardware, or detailed engineering plans, as appropriate. (CDRL A001)

2.1.12 As specified by task order, the Contractor shall develop use cases to document desired operational functionality. The final use cases shall be documented as an update to the existing, deliverable and published with the major release. A TIM shall be held during the use case development to review the progress and status of the use cases before delivery of the draft use case document. Use cases shall be presented during design reviews. (CDRL A024)

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 The Contractor shall develop, implement, and maintain the Quality Assurance (QA) process for developed and sustained CIs as specified by task order. These QA process and procedures (checklists, templates, etc) shall be captured in the QA Plan (or SEMP/SDP as applicable) that includes: objective evaluations of non-deliverable process and products against their applicable plans, process descriptions, standards, and procedures; objective evaluations of deliverable process and products against their applicable plans, process descriptions, standards, and procedures; identifying, documenting, and resolving noncompliance issues prior to delivery; providing feedback to project staff and managers on the results of their activities; ensuring the noncompliance issues are resolved; and maintaining records of QA activities and providing them on the MIS. The QA schedule of activities shall be included in the overall IMS. (CDRL A013, A021, A029, A031, A049)

2.1.15 The Contractor shall develop an engineering model and/or simulation as defined by task order.

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 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 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 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. The Contractor shall develop, document, and implement a small business utilization approach and provide subcontracting reports. The Contractor shall abide by the reporting requirement under FAR 52.219-9 (Individual Subcontracting Report (ISR)/Summary Subcontract Report (SSR)) to include utilizing the Electronic Subcontracting Reporting System (eSRS). The Contractor shall report actual achievement of small business subcontracting results through bi-annual utilization of the eSRS. (CDRL A001, A004, A007, A008, A009, A017, A019, A031, A048)

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, actual vs. planned pseudo-function points, metrics for software baseline management, program issues, status of corrective actions, QA nonconformance resolution, 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; QA schedule of activities; 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® (CMMI) for Development level 4 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. The specific CMMI® version (e.g., V1.2 or V1.3) required will be as specified in task orders. (CDRL A008)

2.2.4 The Contractor shall develop and maintain the Data Management processes 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 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 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. 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 Contract. 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 Contract. 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. (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 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 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. 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. 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 (or SEMP/SDP as appropriate). 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, 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 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.