PWS - 8 Jun 12

Attachment 2

PERFORMANCE WORK STATEMENT

FOR

APPLICATIONS, INFRASTRUCTURE AND SYSTEMS SUPPORT, INCREMENT 2 (AISS II)

Amendment 0001 – 8 Jun 12

Contents

Applications, Infrastructure and Systems Support, Increment 2 (AISS II)

INTRODUCTION

Background The Air Mobility Command (AMC) is responsible to the National Command Authority (NCA) through the Joint Chiefs of Staff (JCS) and the United States Transportation Command (USTRANSCOM) for the planning and execution of global airlift and aerial refueling missions during peace, crisis, and war. AMC is also responsible for the coordination and exercise of airlift and air refueling strategy, doctrine, and plans under the direction of USTRANSCOM. Crisis and wartime support are provided to the unified and specified commands. As an Air Force (AF) Major Command (MAJCOM), AMC is responsible to the Secretary of the Air Force and the Chief of Staff, Headquarters (HQ) United States Air Force (USAF), for the accomplishment of peacetime airlift and air refueling services in a manner that will promote the emergency and wartime capability of assigned forces and ensure the support of all Department of Defense (DoD) components. In addition, AMC is also responsible for aero medical evacuation operation.

AMC supports the Air Force Mobility mission--"Global Reach." It is difficult, if not impossible, for United States military forces to deploy rapidly or be supported effectively during employment without the assets and expertise provided by AMC. AMC Command and Control (C2) and In-Transit Visibility (ITV) processes, procedures, and services must be consistent and reliable in peacetime, during contingencies, and throughout the full spectrum of war. Therefore, the Information Technology (IT) resources enabling the efficient and effective management of this C2/ITV capability must also provide these services at the highest levels of availability, integrity, and confidentiality.

Applications, Infrastructure and Systems Support (AISS) is AMC’s answer in meeting these IT challenges by leveraging hardware, software, services, and support resource consolidation. AISS Increment I consolidated 13 support contracts and enabled the first-ever cross-utilization of IT service and support resources in AMC history. AISS II seeks to enhance the level, quality, and depth of services offered while continuing to streamline and improve process, procedure, and service standardization.

Scope The contractor shall provide services and products described in the Performance Work Statement (PWS) in support of the Mobility Air Force (MAF) C2, ITV/ Business Systems listed below. In this document the Mobility Air Force (MAF) C2, ITV/ Business Systems may be referred to as programs or systems. These services and products in total are referred to as Applications, Infrastructure and Systems Support Increment 2 (AISS II). The services being provided are in the form of technical and support tasks associated with MAF C2, ITV/Business Systems, projects, applications, and infrastructures. The contractor will have a direct working relationship with (but no authority over) other contractors.

The current programs under the purview of the existing AISS contract include:

· Advanced Computer Flight Plan (ACFP)

· Consolidated Air Mobility Planning System (CAMPS)

· Commercial Operations Integrated System (COINS)

· Global Air Transportation Execution System (GATES)

· Global Command and Control System (GCCS)

· Global Decision Support System (GDSS)

· Systems Integration (SI)

· Enterprise Information Management (EIM)

Along with Government developed applications, examples of software currently under the purview of the MAF C2, ITV/Business Systems include:

· Sybase Database Management Software

· Oracle Database Management Software

· Microsoft Structured Query Language (SQL)

· Sybase SQL and High Availability (HA)

· Windows Operating Systems

· UNIX / Red Hat Enterprise Linux Operating Systems

· VMWare

· SharePlex

· NetIQ

· SharePoint

· TCL

Purpose This effort will be in the form of technical and support tasks required to enable the readiness state of the systems, infrastructure, and services that satisfies the HQ AMC/A6 mission for the identified programs. This task is decomposed into the following segments:

Contract Administration The contractor shall provide the contract administration and management oversight necessary in support of this contract.

Enterprise Support Services The contractor shall perform the following tasks and will utilize industry best practices, processes and techniques, associated with various software development methodologies, e.g., Agile, Waterfall, and Spiral. These tasks include three areas:

· Enterprise Services Management (ESM) – is the development of engineering solutions for the technologies, procedures, products and services that enable proactive, end-to-end Performance Monitoring, Systemic Configuration Management, Problem Detection & Resolution, and Information Technology Resource Accounting & Allocation.

· Mobility Infrastructure Engineering (MIE) - is the engineering of solutions for new and existing requirements relating to the physical network, processing, storage, appliances, and security devices.

· “No Service Interruption” (NSI) – is the engineering of solutions for ensuring there is no disruption to operational services as releases are fielded.

Mobility Air Force (MAF) C2, ITV/ Business Systems Support Services The contractor shall provide support in the execution of the following tasks:

· Program Management Office (PMO) Lifecycle Process Support

· Program Level Configuration and Asset Management

· Technical Support and Engineering Services

· Security and Information Assurance

· Client Support Administrator/Functional System Administrator (CSA/FSA) Support

· Testing Services

· Training Services

TECHNICAL REQUIREMENTS

Process support services Contract Deliverable Documentation This section contains documents, products, and deliverables expected from the contractor. Deliverables are directly traceable to the contract support services.

The contractor shall accomplish the following tasks in the manner and schedule described in this PWS. The contractor shall provide process support and prepare, submit, and maintain the documents as outlined below.

Deliverables

Monthly Status Report (A007)

Technical and Management Work Plan (A001)

Contractor’s Progress, Status and Management Report (A002)

Management Plan (A006)

Quality Plan (B010)

Funds and Labor Expenditure Report (A003)

Integrated Master Schedule (A005)

Agenda and Minutes (A004)

Staffing Plan (A001)

Trip Reports (A011)

Risk Management Plan (A013)

Contract and Task Support Meetings The contractor shall support meetings, processes, and any additional events required by the Government. For example:

· Program Management Review (PMR)

· Technical Working Group (TWG)

· Services Working Group (SWG)

· Engineering Status Review

· Task Management Review (TMR)

· Scheduling Meetings

· Support ad-hoc teams as directed by respective PMOs

The contractor shall not conduct any external meetings, conferences, presentations, whether planned or ad hoc, to discuss any program requirements, policies, etc., outside HQ AMC/A6 without first obtaining the permission of this contract’s Government lead and/or applicable PMO. Meeting agendas and minutes are required (A004). Trip Reports will be submitted for travel (A011).

Quality Assurance Program The contractor shall establish and maintain a contract Quality Assurance Program in compliance with the Government Quality Assurance Program (B010).

· Procedures and Practices: Plan, develop, and implement procedures and practices to ensure full and consistent compliance with all requirements of the contract.

· Reporting: Include all Quality Assurance (QA) activities in the Monthly Status Report (A007).

Risk Management The contractor shall describe in a Risk Management Plan, the procedures used for managing areas of risk to ensure successful project completion. The following major risk areas shall be discussed in the Risk Management Plan (A013):

· Net Centric Warfare: In an ever changing environment which is focused on the network and information use, the contractor must show a thorough knowledge of net centric tenets and how different aspects of net centric warfare induces or reduces risk.

· The contractor must show how they propose to mitigate risk associated with changes to the systems.

Upon contract award, the contractor shall continuously monitor and report on the areas of potential risk and provide risk mitigation strategies to the Government as soon as the risk is identified. Risks will be documented in the Monthly Status Report.

Enterprise SUPPORT SERVICES This section pertains to the tasks and work specific to engineering efforts defined by ESM, MIE and NSI. The contractor shall provide the support necessary to maintain and mature the technical solutions via the Government’s approval process. The contractor will apply, manage and maintain these solutions, as necessary, to all environments to include; Exercise, Testing, Training, Prototype, Engineering, and Operational.

Contract Deliverable Documentation This section contains documents, products, and deliverables expected from the contractor. Deliverables are directly traceable to the enterprise support services.

The contractor shall accomplish the following tasks in the manner and schedule described in this PWS. In the absence of specific contract or Government requirements, the contractor shall use software and hardware industry standards and industry best practices. The contractor shall provide process support and prepare, submit, and maintain the documents as outlined below:

Deliverables

Configuration Management Plan (B011)

Topology and Connectivity Diagram (B014)

Facility Drawings (B015)

Scientific and Technical Report (Technology Refresh Plan) (A009)

Computer Software End Items (Special Release Guide) (B009)

Scientific and Technical Report (Post Installation Reports) (A009)

Computer Software End Items (Installation Procedures) (B009)

Computer Software End Items (Operations Documentation) (B009)

Version Description (B005)

Database Design Description (DBDD) (B004)

Interface Design Description (IDD) (B003)

Interface Requirements Specification (IRS) (B002)

Engineering Plan (B001)

System/Subsystem Design Description (SSDD) (B006)

System Architecture Diagrams (B016)

Computer Software End Items (Version Release Kit) (B009)

Change Requests /Problem Reports (B007)

Request for Deviation (B008)

Test Specifications/ Cases/ Recommendations (C002)

Test Descriptions (C002)

Rough Order of Magnitude (ROMs)/Cost Proposals (A014)

Computer Software End Items (System Operator’s Manual) (B009)

Computer Software End Items (B009)

Scientific and Technical Report (Technical Proposals) (A009)

Baseline Descriptions (B012)

Test Reports (C001)

Technical Proposals The contractor shall prepare technical proposals.

Cost Proposal/Rough Order of Magnitudes (A014) The contractor shall prepare cost proposals.

Contractor Configuration Management Program The contractor shall implement Configuration Management (CM) actions across the entire life cycle for both products and services engineered, operated, and maintained by the contractor, following Government guidance and business best practices.

Following industry best practices, the contractor shall establish and maintain a Configuration Management Plan (CMP) (B011) for all products and services within the contractor’s responsibility. The contractor shall provide evidence that the CMP’s processes are effective in controlling Government requirements, tasks, and resources; and that they are being followed. For example, this could be provided by responding to a request by a program for a baseline configuration.

Following industry best practices, the contractor shall implement enterprise configuration management processes for hardware, software, baselines, and documentation. CM shall establish a library for maintaining documentation, technical drawings and software/device configurations, and implement procedures for controlling the elements residing within the library.

The contractor shall ensure their CM proactively controls system and software configurations. The contractor shall deliver software/system products originated within this PWS to the Government for physical configuration audits, and shall take positive actions to ensure correction of any discrepancies noted.

CM requirements pertaining to program support services are identified in paragraph 2.3.2 below.

Product and Services Support The contractor shall provide programmatic, engineering, modernization, and technical support services for all supported systems (A009). Product and Services Support efforts shall fall under three general categories: Enterprise Services Management, Mobility Infrastructure Engineering, and “No Service Interrupt.”

Enterprise Services Management ESM is comprised of the technologies, procedures, products and services that enable proactive management, end-to-end performance monitoring, CM, problem detection and resolution, and information technology resource accounting and allocation. ESM includes the following types of services:

· Network Infrastructure Management

· Appliance Management

· Component/System-level Configuration Management

· Operating Systems Management

· Database Management

· Government Off-the-Shelf/Commercial Off-the-Shelf (GOTS/COTS) Application Management

· Application Performance Management

· Platform Management

· Uninterruptable Power Supply (UPS) Management

· Facility and Environmental Services Monitoring and Management Mobility Infrastructure Engineering MIE is comprised of the actual physical network, processing, storage, appliance, and security devices which enable the systems to operate as intended. MIE includes the following types of devices/services:

· Windows and UNIX based servers

· Network devices, such as switches and routers

· Security, Information Assurance, Authentication, Auditing, and Archiving

· Automated Cross-Domain Solutions

· Firewalls and Proxies

· Storage Area Networks (SANs) and Storage Arrays

· Administrative devices

· Wide area and local area load balancers

· Automated Backup Solutions

“No Service Interruption” NSI support is comprised of developing and delivering the scripts and procedures required to ensure there is no disruption to operational service as releases are fielded. (A009, B009) Programmatic and System Architecture Support The contractor shall provide programmatic and system architecture support by accomplishing the following tasks (A009) (B016):

· Develop baseline description documentation for all products and services engineered (B012).

· Develop and update schedules to support all engineering activities (A005).

· Satisfy Air Force, Joint, and Federal Agency certifications.

· Ensure compliance with DoD Net-Centricity Strategy and USTRANSCOM Enterprise Architecture.

· Develop technology proof-of-concepts.

· Define and document system upgrades to the MIE environment.

· Participate in engineering and validating architecture components.

· Produce design and engineering documentation for all products engineered.

· Ensure the Configuration Management Database and/or Change Request Database is updated to reflect all approved changes.

Upgrade and Modernization Support Following industry best practices, the contractor shall provide and follow its Technology Refresh Plan (A009) that includes the contractor’s approach to analyze, design, engineer, and test the technical releases, described in the following subtasks. Version control will be maintained for all releases (B001, B005).

Releases will be delivered as needed by the Government. Systems’ and projects’ requirements lists for each release are identified in the Release Specification Agreement (RSA). The details for the individual requirements are maintained in the appropriate program database. (Figure 1 depicts the lifecycle events. The details are addressed in the PWS paragraphs).

Based on guidance from the Government and in coordination with stakeholders, analyze, plan, and recommend system requirements and timing for the insertion of new technology via the RSA and baseline description (A009, B005, B006, B012).

Figure 1 Lifecycle

Requirements Support Provide a specific list of requirements necessary to modify, expand, or correct operation of these capabilities by accomplishing the following tasks:

· Account for Security and Information Assurance (IA) requirements during this activity; applicable DoD standards must be subscribed and adhered to through this phase and all subsequent phases of the lifecycle.

· Based on guidance from the Government and in coordination with stakeholders, analyze, plan, and recommend system requirements and timing for the insertion of new technology via the Requirements Management process.

· Prepare formal change requests containing descriptions and specifications of recommended technological requirements or enhancements, to include scope, details, and system interfacing requirements (B007).

· Develop a cost projection for incorporating each requirement identified in the Requirements Specifications into the appropriate Missions System (to include engineering, testing, and fielding) and present to the Government for approval (A014).

· Participate in the RSA process.

· Project a schedule for each RSA within a time period agreed to by the Government.

· Where appropriate, and with Government approval, engineer solutions for problem reports identified in the RSA to correct noted deficiencies from previous releases.

· Support agile development methods.

· Support DoD and AF Cloud and Virtualization Computing strategies.

Analysis Support Provide analysis support by accomplishing the following tasks:

· Prepare functional and technical use cases for each software and hardware requirement (C002).

· Analyze existing functional and technical use cases, and propose refinements to the same, and submit change requests or problem reports in accordance with business practices, processes, procedures, systems, and performance measures (B007).

· Provide recommended changes to RSAs.

· Analyze, define, and recommend system(s) enhancements, to include scope, details, interfaces, and timing of the technical insertions. This activity requires working and coordinating with all stakeholders, staff, and Government contractors, to include hardware suppliers and third party application developers (B003, B014).

· Evaluate and recommend fixed and deployable network topologies and connectivity within existing Mobility C2, Transportation, and Air Operations family of systems to include Local Area Networks (LANs), Wide Area Network (WANs), communications systems, and related systems (B001, B014, B016 ).

· Support Joint Application Development (JAD) sessions when deemed necessary for refinement of requirements; provide minutes from all sessions with any proposed changes to business practices, processes, procedures, systems, performance measures, or changes to technical approach or content. No further action is to be taken from a JAD session without written approval from the Government or designated representative (A004).

· Based on analysis, provide or recommend modifications to the test pass/fail criteria for each RSA requirement for insertion into the RSA and Enterprise test and evaluation plans.

· Conduct requirements review with Government or designated representatives to obtain approvals of techniques and decisions.

Design Utilizing industry best practices, design and document solutions to meet requirements by completing the following tasks (A009, A014, B004, B005, B006, B002, B003, B014, B016):

· Account for Security and IA requirements during this activity. Applicable DoD standards must be satisfied by activities in this phase and all subsequent phases of the lifecycle.

· Design solutions to meet specifications and requirements approved by the Government for each RSA item.

· Design proposed system architectures to include all information flows and all applicable business rules (B016).

· Design, update, and provide Configuration Management of the Logical Data Model and Physical Data Model (LDM/PDM) products.

· Use Government reference data source, currently provided by USTRANSCOM Reference Data Management (TRDM) System, as the authoritative source of system reference data.

· Participate in the Services Working Group to assist the Government with the sustainment and configuration management of the Government provided enterprise-level LDM and the Data Dictionary.

· Participate in the Architecture Data Integration Group (ADIG) to assist the Government with the sustainment and configuration management of the Government provided enterprise-level LDM and the Data Dictionary.

· Assist the Government in the identification, creation, update and/or deletion, and documentation of reference data, e.g., port names.

· Conduct functional and technical design reviews with Government or designated representatives using prepared design products to obtain approvals of direction and decisions.

Engineering Engineer technical solutions to maintain the capabilities described in existing system or software documentation and to implement/transition downward-directed, mission-essential requirements to an operational state. The scope/size of each release is based upon the Government requirements process that prioritizes the requirements to be included in the release based upon constraints such as time and funding. The Program Management Office then formalizes what requirements are officially included in the release. It should be understood that all requirements are not equal in level of effort required to implement and cost to implement. Utilizing industry best practices, engineer solutions from designs accepted by the Government by completing the following tasks (A009, B009, B014, B016):

· Account for Security and IA requirements during this activity. Applicable DoD standards must be satisfied by activities in this phase and proven in the remaining phases of the lifecycle. Develop, test, and document solutions, including refinements of business rules, that do not interfere with currently-fielded systems and releases.

· For engineered solutions provide sustainment and CM of the LDM/PDM.

· Maintain the engineering environment to the most current operational environment configuration

· Validate the intended release environment configuration prior to commencing engineering.

· Coordinate immediately with the Government designated representatives when deviations to the intended environment configurations are necessary to support the engineering effort (B008).

· Engineer, test, and document solutions, including implementation of business rules such that it performs satisfactorily on Government provided equipment.

· Ensure that engineered solution does not interfere with currently fielded hardware or Government accepted software.

· Ensure a schedule is maintained in conjunction with the Integrated Master Schedule to encompass all items approved for engineering and associates each item to a target release schedule. Manage engineering of each item to ensure each item is ready to incorporate into its intended release (A005).

· Perform and validate all required Security and IA best practices during ALL subsets of solution engineered.

· Conduct design and technical reviews with Government or designated representatives to ensure the technical solution meets design specifications and is ready for testing.

Testing Utilizing industry best practices, conduct the following testing tasks to ensure the engineered solution meets all prescribed requirements (C002):

· Procedures must account for validation and verification of Security and IA aspects of the technical solution.

· Produce and maintain test cases and test descriptions.

· Prepare test pass/fail criteria for each RSA requirement.

· Perform testing (e.g. unit, system, interoperability, regression, security, performance, load, exception, and system degradation) to ensure the solution meets the RSA specifications and does not interfere with currently fielded Government-accepted software. The contractor shall include use of automated regression testing techniques and utilities as part of a continuous software integration process.

· Conduct and participate with Government representative in verification and validation testing, to include regression testing, to ensure the capability is suitable for delivery to the Government as the test baseline (TBL).

· Provide to the Government all testing artifacts (e.g. simulators, models, test results, test descriptions, Test Readiness Review (TRR) documents, and data) and tools (manual/automated) required to complete all Government acceptance testing.

· Prepare and deliver test reports for each release to include summary of test results, including all required components and documentation (C001).

· During internal integration testing, allow Government representative to collaborate with test members to help determine if the solution is suitable for delivery to the Government.

· Participate with the Government to complete and document any DoD, Joint, Air Force or other governing body certification and accreditation testing for all security classification domains.

· Perform collaborative testing.

· Perform Government acceptance testing, with direct Government oversight, to demonstrate solutions meet criteria as identified in the RSA.

Engineering Delivery Process The contractor will document in their CMP their Government approved process for packaging, storage, handling and delivery of baselines, technical solutions and all supporting documentation/configuration files, testing, fielding, installation plans, diagrams, system operators manuals, and turnover notices (B009, B011, B012,B014, B015, B016). All artifacts shall be delivered to CM, approved through the Configuration Control Board (CCB) process, and stored in the CML.

Enterprise Impact Mitigation Support the AMC Enterprise by ensuring the technical solution does not adversely affect the existing operational environment, as well as other in-coming technical solutions within their respective test phase of the lifecycle:

· Prepare and deliver the configuration of the intended system (B014).

· Prepare, document and deliver the TBL version and patches for the intended system (B012).

· Demonstrate the solution integrates successfully into the existing systems.

· Provide applicable training and documentation for key technical, functional, Help Desk/Support Center, Training, and Testing personnel, which will consist of both Government and contractor staff.

Security Practices Security practices shall be incorporated into all phases of the engineering lifecycle, including the initial planning activities, based on Government standards and industry best practices and guidance.

· Government approved security scanning and testing, provided by the 375th CSPTS (or its successor/designated agencies), shall be conducted against installed software and hardware within the contractor’s engineering environment.

· Identified security vulnerabilities shall be corrected/mitigated. Security testing results shall be available to the Government for review prior to delivery for inclusion in the DoD Information Assurance Certification and Accreditation Process (DIACAP) package.

· The contractor shall use security analysis and testing and its results as an ongoing, integral part of the engineering process.

Assurance Best practices shall be employed to protect critical Government assets from cyber threats and to ensure the integrity of all engineered items and related materials:

· Engineering efforts shall incorporate practices to assure that engineered solutions and associated critical design information are protected from unauthorized access, manipulation, and exfiltration.

· The contractor’s engineering environment and engineering plans and procedures will be evaluated by the Government prior to the start of engineering activities.

· Engineered solutions will be placed under configuration management and version control.

· Appropriate management processes, access controls, monitoring, and auditing shall be present within the environment to identify threats and vulnerabilities so they are not introduced into the environment.

· Ensure access to/from the isolated engineering environment does not occur except through approved devices specifically allocated for engineering use.

· Monitoring and auditing shall be of sufficient depth and detail, as detailed/performed by the designated Government security agency, using Government approved intrusion detection products and procedures (Network Intrusion Detection System - NIDS and Hardware Intrusion Detection Systems - HIDS) to actively detect inadvertent network traffic or unapproved changes to software, operating systems, or other components of the engineering environment.

· The contractor shall assist the Government security Point of Contact (POC) to ensure appropriate monitoring and incident management procedures are present and continuously enforced within the environment and incidents are reported within 24 hours to the Government security POC.

· Necessary engineering and testing activities that must rely on external sources shall be controlled using strict configuration management practices to ensure security of the environment.

· Any external access to the contractor’s isolated engineering environment shall be documented for review and approval by the Government prior to operation. Industry firewall management best practices shall be employed to protect the environment, such as whitelisting, blacklisting, static IP addressing, etc.

MAF C2, ITV/Business Systems SUPPORT SERVICES This section is dedicated to tasks and work specific to MAF C2, ITV/Business Systems support. Effort is normally traceable to the requesting PMO and may include creation of support documents and artifacts, support of meetings and conferences, training, testing, fielding, CM, asset management, and engineering support for prototyping, testing, training, exercise, and production environments (A012).

The contractor shall provide the following services for all programs.

Program Management Office Documentation Support The contractor shall provide support to the MAF C2, ITV/Business Systems in the following capacity. Deliverables are directly traceable to the PMO documentation support services. The contractor shall assist in development, coordination, and maintenance of program-level documents and artifacts, agreements/memos with outside agencies for allied support, system connectivity, and enterprise interfaces and information services. The contractor shall provide input, coordination and tracking support for program agreements (A015).

Deliverables

Memorandum of Agreements/Understanding (A015)

Scientific and Technical Reports (Task Transition Plan) (A009)

Scientific and Technical Reports (A009)

Configuration Management Plan (B011)

Scientific and Technical Reports (Technology Refresh Plan) (A009)

Topology and Connectivity Diagram (B014)

Service Level Agreements (SLAs) (A015)

Project Support Agreements (PSAs) (A015)

Scientific and Technical Reports (Fielding Plans) (A009)

Monthly Activity Reports (Asset Management – Equipment Inventory Records) (A008)

Asset Management Reports (Annual Inventory Report) (A008)

Physical Configuration Audit Reports (B017)

Baseline Descriptions (B012)

Continuity of Operations Plan (COOP) (A010)

Conference / Demo Support Plan (A012)

Asset Management Plan (B013)

Engineering Plan (B001)

Facility Drawings (B015)

System Architecture Diagrams (B016)

Configuration Management The contractor shall provide robust CM for all MAF C2, ITV/Business Systems, following Government guidance and business best practices, accomplishing the following:

· Be the source of truth for all programs’ test and production baselines (B012). Provide program specific CM information to the PMO upon request. Develop and implement a Government approved archive process for out-of-date baselines.

· Provide CM of all hardware, software, documentation, and configuration baselines from Government acceptance from the developer through operational fielding. For non-production environments CM responsibility is through end-of-life.

· Provide, manage, and implement a Configuration Management Plan (CMP) (B011) that encompasses the contractor’s support efforts of the MAF C2, ITV/Business Systems as outlined in this PWS. This plan shall address management and processes to assure control of test, training, production, exercise, and prototype system configurations as well as providing accurate tracking and reporting of all hardware, software, documentation, configurations, contract deliverables, materials, and Government property for all supported systems.

· Ensure that CM proactively controls system and software configurations.

· Ensure configuration control is implemented for all items identified by the Government for configuration control. Recommend to the Government any additional items to be tracked.

· Maintain a CM database tracking all configuration items (CIs) for each of the supported environments, ensuring the status of all baseline CIs are kept current.

· Update the Change Request (CR) database with additions or changes for any CM items for the MAF C2, ITV/Business Systems.

· Maintain a Configuration Management Library (CML), storing baseline software, configuration files, program environment documentation, Host Nation Agreements, release documentation, asset documents, records, and artifacts. Maintenance of the CML includes ensuring the CML is up-to-date, maintains document control and software management (GOTS, COTS, configuration files and scripts), and maintaining a current backup. CML services include controlling submission of items to the CML, tracking the items in the CML, obtaining the inventory list from the CML tracking system, comparing the inventory list to the CML, resolving configuration item discrepancies, and sending an annual inventory report to the PMO (A008).

· Following industry best practices, develop, implement, and maintain CM plans, processes, procedures, and tools required to provide CM for the systems. Include processes and procedures for software turnover audits, management of the TBL through release of the production baseline (PBL), sustainment of the PBL, and formal turnover of the PBL to Operations and fielding (B011, B012).

· Perform a Physical Configuration Audit (PCA) on the delivered TBL prior to the fielding CCB to ensure the Government has received the documents, software updates, and all other subcomponents necessary to successfully field the release, patch, or hot fix. Provide the appropriate PM a report stating the results of the audit and follow-up on all action items until closure (B017).

· At the completion of testing, conduct a configuration audit to verify the following:

· The necessary hardware upgrades/changes have taken place.

· The necessary COTS licenses have been purchased.

· The necessary infrastructure changes/improvements have been made.

· All Security and IA certifications are current.

· Coordination with relevant agencies and offices has taken place.

· Track the current status of fielded baselines, updating the PMO as requested.

· Develop, implement, and maintain configuration control processes for all testing, prototyping, engineering, exercise, and PBLs (B012).

· Perform software and hardware turnover audits to ensure all necessary items/documentation are received from the developer and engineers. Document the results of these audits and notify PMO of all discrepancies.

· Coordinate and conduct TRRs (waiver required if not performed by CM).

· Control, track and maintain documentation of the approved TBL and patches delivered during testing, ensuring the integrity of the approved baselines that are promoted to the PBL.

· Schedule and facilitate Fielding CCBs for approval to release. Act as secretariat for the boards, update the appropriate databases reflecting the decisions of the boards and publish the minutes of the CCBs within five business days (A004).

· Prepare documentation identifying the PBL components (hardware, software, configurations and documentation) and formally turn the officially approved items over to the Operations and Maintenance (O&M) CM (currently the 375th CSPTS) and fielding teams. Should any be identified, resolve all issues they identify in their audit of the delivery.

· Maintain a copy of the TBL and approved patches prior to it becoming PBL.

· Maintain the current PBL plus two previous in the CML. Maintain an archive of older versions.

· The contractor will track distribution of baseline and AISS-owned software licenses or identify where the baseline software licenses are tracked.

· Notify the PMOs monthly of licenses and maintenance/warranteeagreements that will expire within one year. If the agreements have not been renegotiated, notify the PMOs again at six months.

· Provide Document Control services to ensure centralized management and version control for all systems’ documents. Document Control services include filing documents in the configuration management library, logging the documents into the applicable databases and notifying affected functional areas of document delivery.

· Provide input to the PMO’s DIACAP, Department of Defense Instruction 8510.01.

· Perform CM Status Accounting: Track and report on all CIs formally identified and controlled. Gather, correlate, maintain, and provide the status on the CIs (hardware, documentation and software CIs), and on CM tasks. This includes a listing of the approved configuration identification, the status of proposed changes to the configuration, and the implementation of approved changes. This provides information/data for reporting the status of the baselines, CM metrics, CM activities, and CM audits.

· Conduct CM audits. Document and communicate results with relevant stakeholders.

· Store the results of all audits in the CML, notify the MAF C2, ITV/Business Systems PMO of the results in writing within 5 business days, noting any discrepancies and actions taken to mitigate them and track discrepancies to closure.

· Ensure resolution of noncompliance issues, escalating any issues that cannot be resolved within area of responsibility.

· Collects, analyzes, and reports metrics.

· Provide training to members of the team on CM procedures according to the CMP.

· Release software and engineered solutions in accordance with (IAW) release instructions and/or PMO instructions.

· Maintain a current listing of all approved baselines (B012).

Asset Management The contractor shall provide maintenance and support to control the entire asset life-cycle, from procurement to retirement. Assets, which includes, applications, software, license agreements, infrastructure and hardware, as well as support equipment. Provide asset inventory and asset tracking services that track the financial aspects of an asset to include cost and depreciation as well as contract management aspects including leases, maintenance/warrantee agreements and service contracts. The contractor shall:

· Develop Asset Management Plan (B013).

· Provide robust asset management for all programs by accomplishing the following:

· Maintain an asset management system, ensuring the status of all program assets worldwide, are kept current. All hardware/software received, including assets shipped to other locations, will be tracked, identifying their configurations, the destination location and POC, person receiving it, licenses/maintenance/warrantee agreements, and date of shipment.

· Maintain Government equipment accounts, Automated Data Processing Equipment (ADPE) in the Assets Inventory Management (AIM) IAW AFI 23-111 Management of Government Property in Possession of the Air Force and AFMAN 23-220 Reports of Survey for Air Force Property. Track and account for all Government equipment through the Air Force AIM system and in the asset management system (Access to Air Force AFIs and other official documents is available at http://www.e-publishing.af.mil/).

· Provide inventory control of hardware assets. Inventory control includes appointment of equipment custodians (ECs), receiving hardware assets, performing an annual inventory, maintain accountability, properly disposing of hardware assets as directed, adding, deleting, and updating the asset management databases in a timely manner, and providing written documentation of completed inventory IAW AFI 33-112, Information Technology Hardware Asset Management.

· Support common practices for ordering assets, tracking orders and assets, and (for hardware/equipment), tagging the assets. Interface at various organizational levels in order to support this task. As the subject matter expert, provide Government with recommendations for improving processes and procedures.

· The contractor will maintain a current inventory of all assets and their locations and will provide the inventory to the Government (A008).

· Ensure the PMOs and Equipment Custodians have access to the asset management database to add or update all assets installed at other locations not supported by the contractor.

· Function as a single point of contact for any equipment issues.

· Ensure O&M functions have access to the warrantee/maintenance information available in the asset management database.

· Manage hardware maintenance/warrantee agreements by soliciting bids from qualified hardware maintenance vendors to determine the lowest maintenance/warrantee cost while avoiding diminished support and/or productivity.

· Provide local equipment custodial duties. (Local equipment custodial duties cover equipment within the 100 mile radius of Scott AFB).

· Support the disposition and disposal of assets to include the processing of lost/stolen/destroyed assets and lease expiration activities.

· Maintain equipment; ship and receive equipment; maintain shipping, receiving and accounting documentation.

· Ensure logistics support for other than North Atlantic Treaty Organization (NATO) countries comply with the International Agreement of the host nation.

· Ensure technical data submitted with limited rights, restricted rights, and copyrights shall be marked in accordance with DFARS 252.227-7013. For other deliverable items, marking shall be in accordance with MIL-STD-129 current edition, “Marking for Shipment and Storage.”

· Preservation, packaging, and shipping of deliverable items shall be in accordance with the contractor’s best commercial methods to prevent deterioration and damage during shipment, handling, and storage and to ensure safe arrival at destination.

· Ensure distribution markings are in accordance with the latest edition of DoD Directive 5230.24.

· One of the duties of the contractor is to move equipment (approximately twice per week), in the local area (within the 100 mile radius of Scott AFB). A Government vehicle will not be provided. The contractor accepts transfer liability when transporting the equipment.

· Develop, implement, and maintain a Government approved process to be followed for delivery of items received.

· Develop, document, and maintain shipping processes.

· Coordinate, operate and maintain the local equipment storage facilities located on or around Scott AFB. The operation of these facilities consists of storing, in an organized manner, tracking, delivery, and disposal of equipment for Scott AFB and the local area (100 mile radius around Scott AFB).

· Manage software license agreements optimizing software expenses, while remaining compliant with the agreements’ terms and conditions. Include the general terms and conditions, benefits, strategic and tactical directions, license ordering information, internal billing process, pricing and deployment and support of the products included in the agreement. Respond to questions and issues from the Government and initiate the discussion of issues with the supplier.

· Support negotiation of software license agreements with suppliers to obtain quotes, favorable terms, conditions and pricing.

· Support procurement activities in the direction of software products identified as “approved” or “alternative” and advise which products have been identified as “avoid.” Support programs with the responsibility for determining the strategic use of software products.

· Support application installation, application operations, customer support, training, application maintenance and sustainment and configuration control. This includes the procurement of supporting hardware and software licenses

· Maintain familiarity with the current Information Technology Asset Management (ITAM) Handbook (AFI 33-112 and AFI 33-114).

Technical Support and Engineering Services Provide Technical and Engineering Support Services to all MAF C2, ITV/Business Systems by performing the following:

Technical Administration and Environment Support Provide Technical Administration and Environment Support services to the Production Environment and Non-Production Environment.

Production Environment Support The contractor shall provide production environment and infrastructure support by accomplishing the following tasks while observing Air Force, USTRANSCOM, and DoD Net Centric Environment standards for all designated security classifications.

Production Sustainment Activities

· Provide 24/7/365, on-call Level 3 Technical and Engineering Support of the production environment and infrastructure.

· Coordinate all scheduled maintenance outages with appropriate agencies.

· Execute performance tuning.

· For Global Command and Control System (GCCS), to enhance Active Duty Level 2 Journeymen technical proficiency and improve existing technical incident resolution performance, the contractor will augment Level 2 technical staff with GCCS System Administration Subject Matter Specialists. Specialists must possess and maintain advanced, comprehensive knowledge of GCCS Systems and network operations.

· In observation of AF, USTRANSCOM and DoD policies, the contractor shall maintain, update, and exercise system Contingency Plans/Continuity of Operations Plans (COOPs) and environments according to the…