ALMSS_PWS_-_18_Oct_2016.pdf

PR: FD2399-17-00129 PWS REVISION: 0 1

Performance-Based Work Statement for Support of

Automated Logistics Management Support System (ALMSS)

FD2399-17-00129

AFLCMC/HBG

750 Third Street (Building 350)

Robins Air Force Base, Georgia 31098

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

PR: FD2399-17-00129 PWS REVISION: 0 2

TABLE OF CONTENTS

1.0 DESCRIPTION OF SERVICES………………………………………………………

1.1 Objective(s)…………………………………………………………………………... 4

1.2 Benefit to United States Air Force (USAF)………………………………………

2.0 SERVICES SUMMARY (SS)………………………………………………………………. 4

3.0 GOVERNMENT PROPERTY AND SERVICES………………………………………… 7

3.1 Government Property……………………….…………………………………

3.2 Government Property to be Provided..………………………………………………. 7

3.3 Base Support…………………...…………………………………………………

3.4 Reporting of Government Property………………………………………………

3.5 Loss of Government Property………………………………………………………... 8

3.6 Return/Retention of Government Property..…………………………………………. 9

3.7 Government System(s)………………………………………………………………. 9

3.8 Uses and Safeguarding of Personal Information……………………………………... 9

4.0 ENGINEERING, LOGISTICS, AND TECHNICAL SERVICES……………………….. 9

4.1 Program Management Support………………..……………………………………... 9

4.2 System Support………………………………………………………

4.3 Operational Systems Support………….…………………………………………… 12

4.4 Network Related Support….……………………………………………………

4.5 Software Management and Administration Support…………………………………15

4.6 Logistics Support………………………………..………………………………

4.7 Training Support…..………………………………………………………………... 18

4.8 Inventory Support…………………………………………………………………... 18

4.9 Quality Assurance Provisions……………………………………………………... 18

4.10 Configuration Management (CM) Plan…………………………………………… 18

4.11 Program Management Plan (PMP)………………………………………………... 19

4.12 Period and Place of Performance………………………………………………….. 19

4.13 Packaging………………………………………………………………………….. 19

4.14 Counterfeit Electronic Parts………………………………………………………. 19

4.15 Travel……………………………………………………………………………… 20

4.16 Holidays and Facility Closings.…………………………………………………… 22

4.17 Work Hours………………………………………………………………………... 22

4.18 Contract Surveillance……………………………………………………………… 23

4.19 Contractor Personnel………………………………………………………………. 23

4.20 Contractor On-Site Management………………………………………………….. 23

5.0 GENERAL INFORMATION…………………………………………….……………….. 23

5.1 Continuation of Mission-Essential Services During a Crisis……………………

5.2 Security Requirements……………………………………………………………… 24

5.3 Environmental Management System……………………………………………

5.4 Affirmative Procurement Programs………………………………………………… 27

5.5 Safety Requirements……………………………………………………………….. .27

5.6 Inspection of Services………………………………………………………..…….. .28

5.7 Trafficking in Persons………………………………………………………………. 28

TABLE OF CONTENTS (Cont'd)

PR: FD2399-17-00129 PWS REVISION: 0 3

5.8 Contractor Manpower Reporting…………………………………………………… 29

5.9 Invoicing/Payment and Receipt/Acceptance……………………………………

5.10 Transition Plan…………………………………………………………………….. 29

6.0 APPENDICES……………………………………………………………………………… 31

APPENDIX A: Hardware Requiring Original Equipment Manufacturer (OEM) Maintenance………………………...………………………………….…..………... 32 APPENDIX B: ALMSS Government-Furnished Equipment (GFE)…………………… 33 APPENDIX C: ALMSS Commercial-Off-The-Shelf (COTS) Software…………..…... 34 APPENDIX D: References……………………………………………………………... 35 APPENDIX E: List of Operating Locations……………………………………………. 38 APPENDIX F: CDRL Listing………………………………………………………….. 39

1.0 Description of Services. The Command and Control, Intelligence, Surveillance, and Reconnaissance (C2ISR) Division (AFLCMC/HBG) has a requirement for Automated Logistics Management Support System (ALMSS) support to sustain and improve the

PR: FD2399-17-00129 PWS REVISION: 0 4

effectiveness/efficiency of its worldwide mission providing cradle-to-grave sustainment management for C2ISR systems and other assigned platforms. Requirements are for Supply Chain Management (SCM) software which covers all ISR assets and systems. Included in ISR initiatives are weapon systems capabilities which include maintenance planning and processing, location-specific data, maintenance and usage of parts for better decision-making, increased data accuracy, predictive maintenance preparation, etc. The requirement includes an integrated system which provides our worldwide stakeholders an ability to extract specific details for operations management and logistics information via graphical dashboards, tools, etc. for analysis and decision-making. This requires an ability to integrate comparable system capabilities and applications with our current, Government-owned systems which already interface with various Government applications/systems as mandated. Future requirements will be determined by mission need, refined requirements, and funding as determined constrained by ISR's current and out year priorities.

The C2ISR Division employs a variety of Weapon System Infrastructure technologies, systems, and support to accomplish effective SCM infrastructure and to achieve the sustainment objectives of the C2ISR Division and the operational objectives of its customers. C2ISR-managed weapons systems include, but are not limited to, U2, Air Force (AF) Distributed Common Ground System (DCGS), Joint Surveillance Target Attack Radar System (JSTARS), Predator/Reaper, Data Links, Sensors, Special Projects, and DCGS/Commercial-Off-The-Shelf (COTS) for over 360 users to include Depot, Operating Locations and multiple Contractors.

ALMSS is used to provide common item ordering support for Unmanned Aerial Vehicle (UAVs) and other unclassified projects. ALMSS is also used to provide depot SCM support for items managed by the AFLCMC/EBG Specialized Management Division (QL). Foreign companies, as a prime, partner or subcontractor, are not allowed to participate in this ALMSS requirement.

1.1 Objective(s). Mission requirements include, but are not limited to, providing world-class sustainment, integrated logistics, and the coordination of weapon system acquisition, operational and sustainment support for C2ISR weapon systems.

1.2 Benefit to United States Air Force (USAF). The C2ISR ALMSS support contract benefits the USAF by providing worldwide logistics support to multiple weapon system platforms.

Hence, the Contractor will be responsible for a SCM software which covers all ISR assets and systems. Further, this Contractor Logistics Support (CLS) Contractor will support the rapid flow of cross-functional information and use of parts and materials between the different C2ISR weapon systems.

2.0 Services Summary. This task requires SCM software and hardware technologies, tools, systems, and processes to assure the efficient and cost effective accomplishment of key mission support activities. Supported requirements include, but are not limited to, the Automated Logistics Management Support System (ALMSS), Special Project Closed User Group Networks, Engineering Closed User Group, Logistics Closed User Group, and other tasks related to the weapon system and SCM infrastructure. Elements of this contract require intelligence information access to the Top Secret/Sensitive Compartmented Information (SCI) level.

PR: FD2399-17-00129 PWS REVISION: 0 5

Performance Objective PWS Reference

Performance Threshold

Timely release of block cycle updates

4.5.3 The Contractor shall release block cycle

updates no later than 5 business days after target date for release as agreed upon by the Government and Contractor.

Receipt of Contract Data Requirements List (CDRLs)

App F

There shall be no more than 1 late submission of data/document(s) every 6 months. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by a revised delivery date acceptable to the Government.

Correct Discrepancy Reports (DIREPs) within the allowable timeframes:

Emergency – 15 business days; Priority – 45 business days; Routine – 60 business days

Para 4.5.2 There shall be no more than 2 late responses to DIREPs every 6 months.

Emergency DIREPs shall be corrected within 15 business days;

Priority DIREPs shall be corrected within 45 business days; and

Routine DIREPs shall be corrected within 60 business days unless otherwise agreed upon by the Government PM.

The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Request(s) for assistance Para 4.6.2 Para 4.3.1.2

The Contractor shall initially respond to a Government request for assistance within 2 business days. Follow-up assistance, if required, shall be provided by a suspense date acceptable to the Government.

Operational availability of

ALMSS

Para 4.3.1.6

98% operational availability based on hours calculated quarterly. This excludes routine system maintenance and/or

PR: FD2399-17-00129 PWS REVISION: 0 6

unforeseen occurrences approved by the Government.

Provide ALMSS security support to prevent unauthorized access, upload appropriate security patches as required, and properly “wipe” disk drives and free space in event of a security breach and/or in case of disaster or catastrophic failure

Para 4.3.1.7

100% compliance.

Staff all funded positions within 30 business days after receipt of contract award and 15 business days after position is vacated

Para 4.11 95% of the employees shall meet PWS (security clearance, skill/experience, education, etc.) requirements. Remaining 5% of this objective shall be met within 45 business days of contract award.

Retain 97% of the workforce Para 4.11 The Contractor shall maintain a 97% retention percentage (calculated monthly, averaged quarterly) at the basic contract level. There shall be no more than 2 employees lost to organizations outside of C2ISR Division.

Contractor Manpower Reporting

Para 5.8.1 Within 30 business days of contract/order award, the Contractor shall establish a record for the contract/order in eCMRA including Order Data, Contact Data and Location Data.

The Contractor shall provide an annual count of contractor/subcontractor personnel performing services and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than October 31 of the following fiscal year.

3.0 Government Property and Services

3.1 Government Property

The Contractor shall be responsible for Government property in their possession in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements including, but not

PR: FD2399-17-00129 PWS REVISION: 0 7

limited to, FAR Part 45, Government Property; FAR 52.245-1, Government Property; and Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, Government Property.

The FAR and applicable supplements can be accessed at this web site: http://farsite.hill.af.mil.

3.2 Government Property to be Provided

The Government will provide a temporary work area at Government installations in the vicinity of the primary duty location, as applicable, to facilitate face-to-face coordination with program office project personnel; the area will be available on a shared basis for a limited number of personnel. The area will include a computer (hardware and software), Internet and base network connection for use of access controlled information, desk, and phone. The Government will furnish Class A telephone commercial and Defense Switching Network (DSN) access, Local Area Network (LAN) access and maintenance support for both. The Contractor shall comply with all security requirements pertaining to telephone and LAN usage and ensure that these services are utilized only for official matters pertaining to this PWS and associated tasks.

Telephone and computer networks are subject to monitoring at any time.

3.3 Base Support

3.3.1 Janitorial Support. The Government will provide housekeeping and janitorial services at Government furnished facilities limited to Contractor office, administrative areas, and restrooms.

This support includes providing supplies for restroom areas. The Contractor shall provide routine housekeeping services within Government furnished facility in the Contractor working areas such as Contractor owned or leased facilities. All Government and Contractor personnel are required to clean the spills and clutter resulting from their use of the refrigerators, microwaves, coffee pots, etc., in the breakroom and snackbar areas. Further, the Contractor shall clean-up work areas when tasks are completed to restore the work area to a clean and usable condition.

3.3.2 Building and Grounds Maintenance. The Government will maintain Government owned buildings and adjacent grounds, parking lots, and roads used in the performance of this contract.

The Contractor shall notify the Government Contracting Officer's Representative (COR) and/or Facility Manager of building or grounds discrepancies (within 1 hour of findings).

3.3.3 Refuse Collection and Disposal. The Government will provide bulk trash containers (dumpster type) in the immediate outside vicinity of Building 350 and will ensure the containers are emptied on a regular basis. Contractor personnel shall empty their work area trash each week in the outside dumpster. The Government dumpsters shall not be used to dispose of construction debris or hazardous material.

3.3.4 Emergency Medical Treatment. The Government will provide only emergency first aid and ambulance services on a reimbursable basis. The Government will not be responsible for hospitalization or other medical services for Contractor personnel. The telephone number is 911 for emergencies. Calling 911 from a cell phone is received by the off-base emergency 911 systems, causing a delay in the response time by emergency personnel. Therefore the caller should request Robins Air Force Base (RAFB) 911. When possible use a base telephone to receive on-base help.

PR: FD2399-17-00129 PWS REVISION: 0 8

3.3.5 Security. The Government will provide normal physical security services covering entry/exit control, Government facilities and equipment located on RAFB.

3.3.6 Fire Protection. The Government will inform the Contractor of the policies and procedures necessary for fire protection consistent with the Government fire protection programs; provide firefighting equipment; provide fire rescue services; conduct facility fire safety inspections;

inspect and maintain portable fire extinguishers and fire protection systems and equipment in the Contractor-occupied facilities; and provide fire-fighting services for Contractor facilities on Government installations. The Contractor shall comply with the fire prevention rules and regulations enforced by RAFB Fire Prevention Branch. Call 911 for emergencies from Government phone or if using cell phone ask off-base emergency 911 to connect to RAFB 911.

3.4 Reporting of Government Property. The Contractor shall create and maintain records of all Government property accountable to the contract in accordance with FAR 52.245-1(f)(1)(iii), Records of Government Property. An annual inventory of all Government furnished equipment/property shall be conducted and a record copy of this inventory shall be available for inspection by the Government Procurement Contracting Officer (PCO) or COR upon request.

3.5 Loss of Government Property

3.5.1 Definition of Loss of Government Property. In accordance with DFARS 252.245-7002, Reporting Loss of Government Property, “loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, theft, loss due to lack of security, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair. Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing.

Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.5.2 Reporting Loss of Government Property. The Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at this site: (http://www.dcma.mil/aboutetools.cfm). The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

3.6 Return/Retention of Government Property. All property provided by the Government remains the property of the Government and shall be returned to the Government upon completion of the contract/order. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order. All Department of Defense (DD) Form

PR: FD2399-17-00129 PWS REVISION: 0 9

1423, Contract Data Requirements List (CDRL), deliverables become the property of the Government upon receipt.

3.7 Government System(s). The Government will provide Contractor personnel access to systems necessary to perform tasks under the contract/order. All Government rules and regulations are applicable. The Government will provide system access subject to approval of the Department of Defense (DD) Form 2875, System Authorization Access Request (SAAR).

Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the system account(s) will be closed.

3.8 Uses and Safeguarding of Personal Information. Information from the secure web site is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will Personally Identifiable Information data be released to the public with the Contractor name and contract number associated with the data.

4.0 Engineering, Logistics, and Technical Services

4.1 Program Management Support. The Contractor shall perform the Program Management (PM) functions necessary to plan, supervise, and execute the tasks within the Performance Work Statement (PWS). The Contractor PM shall demonstrate a detailed understanding of the requirements of the PWS and shall function as the single point of contact for the Government PM. The Contractor PM shall support Government management reviews, assign and monitor task performance of the Contractor team, monitor risks associated with tasks and suggest risk mitigation strategies, provide estimates for performance of in-scope tasks requested or assigned by the Government PM, and ensure project control and reporting for assigned activities. (All CDRLs are listed in Appendix E)

4.1.1 Status Reports: The Contractor shall provide Monthly Status Reports (MSR) of work in progress, preventive maintenance performed and needing to be performed, significant events, discrepancy reports, file clean-up, requirement analysis, software change requests, accounting financial management system updates, individual project updates, Enterprise Information Technology Data Repository (EITDR) information, list of queries created, maintenance and in-commission rates and monthly archive results, status of specific tasks, problems and corrective action taken/recommended. (CDRL A001, Monthly Status Report, DI-MGMT-80368A/T)

4.1.2 Project Control and Reporting: The Contractor shall provide a schedule for each software, hardware, training, or sustainment support project assigned by the Government Program Manager. The Contractor shall verify and track approved costs and schedules to ensure that project activities remain on schedule and within budget, reporting monthly cost data for all associated Contract Line Item Numbers (CLINs) in an accurate and timely manner. (CDRL A001, Monthly Status Report, DI-MGMT-80368A/T)

4.1.3 The Contractor shall maintain coordination and communication with other Government and Contractor-led groups required to exchange data, maintain connectivity, maintain compliance, and remain current with ongoing or planned changes that may impact the supported weapon system support infrastructure of the C2ISR Division. This includes Contractor-Supported

PR: FD2399-17-00129 PWS REVISION: 0 10

Weapon System (CSWS), ESC/HGGG [i.e., Integrated Logistics System-Supply (ILS-S)], ALMSS Financial Improvement and Audit Readiness (FIAR), Defense Logistics Agency (DLA) Transaction Services, Information-Network Operations Security Center (I-NOSC), Air Force Network Integration Center (AFNIC), National Security Agency (NSA), United States (US) Embassy, Air Force Intelligence Surveillance Reconnaissance Agency (AFISRA), Air Force Cryptologic Systems Group (CPSG), and Defense Information System Agency (DISA) entities.

The Contractor shall assist the Government in conducting audits.

4.1.4 The Contractor shall maintain coordination and communication with the AFNIC to exchange data and remain current with on-going or planned information assurance changes that may impact supported systems.

4.1.5 The Government PM will identify key interfaces and tasks to ensure the continued ability of the C2ISR Division to effectively communicate vital sustainment information and documentation throughout its supply chain.

4.1.6 The Contractor shall maintain information for supported systems within the EITDR and the Enterprise Mission Assurance Support Service (eMASS) systems.

4.1.7 EITDR and eMASS support includes maintaining required data in these systems. Support also includes research and documentation support for completion of Statements of Compliance for Budget Estimate Submission, Annual Information Assurance Security Controls Reviews, Annual Security Controls Testing, Annual Contingency Plan Testing, ALMSS Certification and Accreditation Packages, or other related tasks that may be assigned by the Government PM.

4.1.8 The Contractor shall follow the directions of and respond to the Government Information Assurance Officer (IAO) and perform the duties of an Information Assurance Manager (IAM) in accordance with Department of Defense Information Assurance Workforce Improvement Program (IA Training) (DoD) 8570.01-M for supported systems. The IAO/IAM shall be Level II certified within six months of assignment to the position. Personnel who are not appropriately certified within six months of assignment to the position or who fail to maintain their certification status shall not be permitted privileged access (DoD 8570.01-M, Change 4, 10 Nov 2015, Chapter 3). The IAO/IAM will be required to attend meetings, support interface working groups, participate in design/development/deployment activities, or design/modify/implement/support hardware, software, training, or process changes to supported systems.

4.1.9 National Institute of Standards and Technology (NIST) Training will be required for cybersecurity surrounding operations of ALMSS. As agreed upon by the Government the Contractor may need to attend training to understand the NIST requirements and standards.

4.2 System Support. The C2ISR Division weapon system support infrastructure and Supply Chain Management (SCM) activities make use of multiple systems, applications, processes, and tools in performing day to day execution of its global support mission. The systems described and listed below are directly supported, maintained, and sustained through the tasks described within the PWS. The associated tasks that follow are required to ensure the level of system

PR: FD2399-17-00129 PWS REVISION: 0 11

availability necessary to meet operational support and sustainment objectives of the C2ISR Division.

4.2.1 Automated Logistics Management Support System (ALMSS). ALMSS is a certified and accredited web-based integrated wholesale/retail SCM system. It provides global sustainment support in a CLS environment for the U-2 Aircraft, Remotely Piloted Vehicles (RPVs), Unmanned Aerial Vehicles (UAVs), Distributed Common Ground Systems (DCGS), Data Links, Sensors, Special Projects, Commercial-Off-the-Shelf (COTS) for approximately 143 ILS-S locations and 110 COTS locations worldwide, other unclassified projects, and Specialized Management Division programs. ALMSS provides a single database to manage supply requirements from user through Item Manager to Source of Supply (SOS). It supports the high demand weapon system SCM environment providing global logistics support to the war fighter.

The system currently supports approximately 102 COTS users, 129 ALMSS users, and 101 Contractor ALMSS (CALMSS) users (on-site and worldwide remote) performing Depot, Operating Location (OL) and Contractor support functions. ALMSS exchanges data with the ILS-S, ALMSS FIAR, the Defense Logistics Agency (DLA) wholesale system, and the Air Force Stock Control System (D035) through DLA transaction services. ALMSS also exchanges data with the Air Force Master Item Identification Control System (D043), Stock Number User Directory (D071) and the C2ISR Special Projects Logistics Closed User Group (LOGCUG) system. ALMSS is comprised of over one million lines of source code and resides on an IBM System I Server. The application is written in several high level languages including HTML, JavaScript, IRL, JAVA, COBOL, COBOLLE, RPG, RPGLE, CL, CLLE, Progress, ColdFusion, and PowerBuilder. Major processing, receipts, inspection, inventory, shipments, transportation, serialized item control, special item handling, Time Compliance Technical Order (TCTO), file maintenance, financial management, authorizations, Readiness Based Levels (RBLs), interrogations, economic order quantity computations, recoverable computations, purchase directives, purchase requests, work orders, automated document control, Contractor direct shipments, bonded stock, Government-Furnished Equipment (GFE), Commercial-Off-the-Shelf (COTS), field units, archiving, asset tracking, total asset visibility, bar coding, Item Unique Identification (IUID), redistribution order, excess, Air Force Recoverable Assembly Management Processing, Defense Reutilization Marketing Organization, in-transit inbound and outbound tracking, Mission Capable (MICAP) tracking, SURGE reporting, materiel obligation validation, critical item management, reverse post, security, DoD Private Key Infrastructure (PKI) client authentication, end-of-year processing, reports generation and automated distribution through e-mail, Contractor data and cataloging. It is designed to provide a full range of stock control and distribution functionality for both national stock number and part number peculiar items for wholesale and retail distribution. ALMSS will provide Enterprise Information Systems Sustainment (EISS) and related engineering, logistics and SCM support in the form of Operating System support, Database Management Administration, Hardware/Software Maintenance, Logistics support and training, COTS Integration, functional analysis support, program management, operations technical support, and requirements computation administration.

4.2.2 Closed User Group (CUG) Networks. The Special Projects secure communications network consists of the following secure communications network infrastructures: Special Project Closed User Group (SPCUG), Engineering Closed User Group (ENGCUG), and

PR: FD2399-17-00129 PWS REVISION: 0 12

Logistics Closed User Group (LOGCUG). This secure communications infrastructure is a Secure Virtual Private Network (SVPN) protecting unique Special Projects data at the SECRET level.

4.2.2.1 The LOGCUG System is a logistics application that provides logisticians access to unique Special Projects logistics data and is a web-accessible, database-driven application, with off-line bi-directional data feeds into ALMSS. The objectives for support of the CUG networks are to sustain secure communications between various CONUS and OCONUS sites with security adequate to protect information at the SECRET level; designing, installing, and sustaining secure communications capabilities between existing and new sites; and, providing Operations and Maintenance (O&M) documentation and training while maintaining all infrastructure in the same configuration as the original installation. The Special Projects Program Office is the focal point for coordination of communication issues with external agencies and remote users.

4.2.3 Specialized Management Division Programs. Provide logistics manager(s), systems analyst(s), system engineering, technical, customer, and training support needed to establish and maintain SCM services for depot managed items used at various CONUS and OCONUS field locations. Support shall include collaboration and coordination needed to establish and maintain user accounts, establish and maintain support activity addresses, develop and distribute ad-hoc query reports, and provide training/consulting services to Specialized Management Division program personnel.

4.3 Operational Systems Support. To accomplish the PWS and system support objectives, the Contractor shall perform system engineering and operational systems support of the systems described above through effective execution of the following tasks:

4.3.1 ALMSS Support. The Contractor shall perform preventive maintenance and repair of the ALMSS components listed in Appendix A, Hardware Requiring Original Equipment Manufacturer (OEM) Maintenance and Appendix B, ALMSS GFE. The Contractor shall maintain preventive and unscheduled equipment maintenance records on hardware items including peripheral component items in the Government’s possession and associated with this contract. Purchases required under this PWS will require Government approval and signature prior to completing the transactions. The Contractor shall establish and maintain OEM hardware and operating system software maintenance contracts for the ALMSS servers located at both Government and Contractor facilities. The main server and peripherals at the Government facility are mission essential items and shall be repaired/returned to service as soon as possible.

The Contractor shall identify failed equipment items that require warranty or repair actions to the Government. The Contractor shall procure and manage software licenses for the Government on a cost reimbursable CLIN. The Contractor shall obtain approval from the Government PM prior to purchasing software licenses. The Government will reimburse the Contractor for these purchases. The Contractor shall procure required hardware for the Government as needed on a cost reimbursement basis. This includes such hardware peripheral items as ink, toner cartridges, etc. The Contractor shall obtain approval from the Government PM prior to purchasing hardware. Information concerning preventive maintenance and repair actions and software/hardware purchases shall be provided in the Monthly Status Report. (CDRL A001, Monthly Status Report, DI-MGMT-80368A/T)

PR: FD2399-17-00129 PWS REVISION: 0 13

4.3.1.1 The Contractor shall also operate a preventive and scheduled maintenance program to maintain performance of the servers, including warranty items. Scheduled maintenance intervals for system components shall be derived from the vendor’s technical documentation, and scheduled maintenance shall be performed within 10 business days of the scheduled action.

Information concerning preventive and scheduled maintenance actions, to include actions on warranty items, shall be provided in the Monthly Status Report. (CDRL A001, Monthly Status Report, DI-MGMT-80368A/T)

4.3.1.2 The Contractor shall provide a System Engineering POC to receive telephone notification of remedial maintenance from 0700-1700, Monday through Friday, excluding holidays. The Contractor shall provide customer support and troubleshooting/assistance for assigned systems/software. The Contractor shall initially respond to a Government request for assistance within 2 business days. Follow-up assistance, if required, shall be provided by a suspense date acceptable to the Government. The Contractor shall determine whether the malfunction is system-related or network-related. The Contractor shall use Government-directed Information Assurance (IA) tools and databases to request, modify and/or delete Internet Protocol (IP) addresses. Network problems that are determined to be supported system issues shall be corrected by the Contractor using Government-furnished hardware/software tools. The Contractor shall coordinate with the network technical support as necessary to assure resolution of network-related problems. Information concerning calls received and/or contacts made, to include identification of issues and resulting resolutions, shall be provided in the Monthly Status Report. (CDRL A001, Monthly Status Report, DI-MGMT-80368A/T)

4.3.1.3 The Contractor shall attend and participate in program support meetings, Technical Interchange Meetings (TIMs), and other working group/user group meetings as requested by the Government PM.

4.3.1.4 The Contractor shall analyze and make recommendations concerning technology and process upgrades to the Government PM.

4.3.1.5 The Contractor shall plan and recommend changes to improve overall system performance, verify system software configurations, establish system control values for web based applications, test Internet hardware and vendor software modifications to ensure compatibility, load software patches and enhancements, create and monitor output queues, and cross reference and maintain user profiles, web interface routing, and Stock Record Account Number (SRAN) information to ensure correct routing of documents to remote users. (CDRL A002, Software Development Plan (SDP), DI-IPSC-81427A)

4.3.1.6 The Contractor shall maintain supported equipment to support operational requirements of the C2ISR Division and its customers. The Contractor shall provide support to maintain ALMSS hardware, operating system, servers, and application systems. This support requires 98% operational availability based on hours calculated quarterly. This excludes routine system maintenance and/or unforeseen occurrences approved by the Government.

PR: FD2399-17-00129 PWS REVISION: 0 14

4.3.1.7 The Contractor shall implement and monitor a security/recovery strategy and program that includes security safeguards sufficient to prevent unauthorized system access, provides a backup recovery strategy for all ALMSS and CUG data, following an established and Government approved schedule of backups, supports ALMSS system recovery through participation in contingency processing in the event of a disaster (real or exercise), enables offsite transport and storage of vital ALMSS data, and provides a data warehousing function sufficient to provide periodic data restoration points (month end/year end) for supported systems.

The Contractor shall provide ALMSS security support at all times to prevent unauthorized access, shall upload appropriate security patches as required, and, in accordance with Air Force Manual 33-282, dated 28 Mar 2012, shall “wipe” disk drives and free space in the event of a security breach and/or disaster or catastrophic failure. Security support requires 100% compliance.

4.3.1.8 The Contractor shall perform weekly data backups for the CUG systems and store the back-up data in a secure off-site location. The Contractor shall maintain multiple system restore points to include the previous month’s end restore point.

4.3.1.9 The Contractor shall perform server operating system software administration for ALMSS components located at both the Government facility and the Contractor facility and shall function as an administrator for COTS products used by ALMSS. This includes surveillance of integration and operation of COTS interfaces and maintenance of annual OEM software maintenance contracts for the third party software listed in Appendix C.

4.3.1.10 The Contractor shall maintain data file descriptions, develop and distribute ad hoc query reports, maintain records of database tables required in the production environment, maintain multiple ALMSS environments (development/testing/training), perform ALMSS database administration functions, and perform baseline software updates, including upload of corrected discrepancies and Configuration Management (CM) of the production environment.

4.3.1.11 The Contractor shall perform baseline software updates, develop and maintain operations routines, document unique system related tasks and functions, troubleshoot data related problems, make recommendations to ensure data integrity, and assume responsibility for operations and all related tasks to support the ALMSS servers at the Government facility and related equipment at the Contractor facility. (CDRL A002, Software Development Plan, DI-

IPSC-81427A)

4.3.1.12 The Contractor shall maintain and administer website zone authorities, perform website administration including connections, File Cabinet, and High Speed Messaging (HSM) server components, and coordinate with software vendors to troubleshoot and resolve problems related to web interfaces.

4.3.1.13 The Contractor shall perform database integrity analysis on problems that may require significant research to ensure avoidance of database corruption, giving these problems a high priority for correction.

4.3.1.14 The Contractor shall assist an organic source in an ALMSS data package creation project. The Government is planning to establish an organic capability to gain a better

PR: FD2399-17-00129 PWS REVISION: 0 15

understanding of systems architecture and assist with the data reviews and configuration management. The Contractor shall participate as a member of the Integrated Product Team (IPT) and assist with the development of an organic capability within the program office. The IPT shall have daily interaction as the organic capability is developed. The program office's goal for this new organic capability is to gain an understanding of the hardware, software, and systems architecture needed to support the system.

4.3.1.15 The Contractor shall assist in completing Financial Improvement and Audit Readiness (FIAR) audits/assessments, meet compliance reporting requirements, and attend training as approved by the Government PM related to FIAR in support of ALMSS.

4.4 Network Related Support. The Contractor shall provide the engineering, technical, logistics and training services necessary to maintain effective operation of supported systems on networks both within and outside the C2ISR Division infrastructures. Support shall include collaboration and coordination of user account/address changes and requests with the network managers and technical staff; integration, configuration and upgrade of COTS packages or system specific applications on network servers for software related to supported systems;

troubleshooting of connectivity issues for ALMSS within the C2ISR Division weapon system support infrastructure, sustaining acceptable operational levels of services to C2ISR Division applications transferring data to or from supported systems; facilitating electronic transfer of data between supported systems and various DoD-related data interfaces; reporting status of network issues to the C2ISR Division and recommending courses of action; configuring nodes to ensure network addresses are not in conflict with other users; maintaining selected equipment (such as the twin-axial cable between the ALMSS Server and dedicated ALMSS printers); and collaborating and coordinating with network managers and technical staff to maintain compliance and resolve Information Assurance (IA) issues.

4.4.1 System logs for supported CUG systems shall be analyzed for unauthorized access and any incidents reported to the Special Programs/Projects Office (SPPO) on a monthly basis.

4.4.2 Connectivity issues for the SPPO systems shall be coordinated with external communications agencies through the SPPO.

4.4.3 The Contractor shall determine requirements and make recommendations for enhanced connectivity, including requirements for additional sites and increased capability, to the Government PM and/or the SPPO, as requested.

4.5 Software Management and Administration Support

4.5.1 Contractor shall maintain a core software support team to sustain the specified systems.

The Contractor shall perform requirements analysis, functional analysis, software unit testing, system testing, software quality assurance, configuration management, program control, and software programming as necessary. To document the support team, the Contractor shall develop a software development plan. (CDRL A002 DI-IPSC-81427A)

4.5.2 The Contractor shall provide programming, testing and implementation of Procedural Change Requests (PCRs) and corrective actions to correct system discrepancy reports (DIREPs).

PR: FD2399-17-00129 PWS REVISION: 0 16

DIREPs shall be corrected using a priority classification as a determinant of resolution time.

There shall be no more than 2 late submission(s) of data/document(s) every 6 months.

Emergency DIREPs shall be corrected within 15 business days; Priority DIREPs shall be corrected within 45 business days; and Routine DIREPs shall be corrected within 60 business days unless otherwise agreed upon by the Government PM. Emergency DIREPs take precedence over all other programming tasks. Corrected programs must be tested to verify corrections and ensure acceptance by the Government PM or designee before integration into the production environment. User Manual changes resulting from DIREPs shall be made, and a summary of DIREP actions reported, in the Monthly Status Report. (CDRLs A004, User’s Manual, DI-IPSC-81443A and A001, Monthly Status Report, DI-MGMT-80368A/T)

4.5.3 The Contractor shall complete block cycle updates on a schedule to be determined by the Government but no less than 1 per year. Block cycle updates shall consist of discrepancy report (DIREP) corrections, system enhancements, commercial software updates as defined by the Government via a statement of objectives. The Contractor shall maintain a listing of new project requirements and estimates by project for the labor hours required to complete. The Contractor shall work collaboratively with the Government to prioritize the listing. The Contractor shall provide a quote within 10 business days of the Government's request and block cycle updates shall be released no later than 5 business days after the target date as agreed upon by the Government and Contractor. The block cycle update(s) will be funded by the Government using a fixed price CLIN.

4.5.4 For approved new projects, the Contractor shall prepare a Requirements Document (RD).

A programming Design Document (DD) will be developed to identify the software element modifications necessary to accomplish the logistical requirements in the RD. The Contractor shall conduct design reviews appropriate to the complexity of the project. The Contractor shall perform multi-level testing of modified software prior to Functional Configuration Audit/Physical Configuration Audit (FCA/PCA). Updates shall be made to the User’s Manual, as required. The Contractor shall provide the final RD to the Government for approval/signature.

(CDRL A005, Design Review Data Package, DI-ILSS-81335 and CDRL A004, User’s Manual, DI-IPSC-81443A)

4.5.5 The Contractor shall conduct periodic design reviews with the Government throughout the life cycle of each project as mutually agreed to by the Contractor and the Government PM. At a minimum, a Preliminary Design Review (PDR) and Critical Design Review (CDR) should be conducted for major modifications. Minutes of each of these reviews shall be provided to the Government within 10 business days. Reviews may be combined or waived at the written request of the Government. (CDRL A005, Design Review Data Package, DI-ILSS-81335; CDRL A006, Conference Minutes, DI-ADMN-81505)

4.5.6 The Contractor shall conduct acceptance testing for each new project (FCA/PCA). The Government Program Manager or his/her designated representative will attend the final acceptance testing. Once accepted, the Contractor shall provide familiarization training and hands-on training to C2ISR Division personnel, covering any changes made to the configuration item as appropriate to the complexity of the change.

PR: FD2399-17-00129 PWS REVISION: 0 17

4.5.7 The Contractor shall maintain an ALMSS master test question database, to include changes generated by DIREPs and new projects. The Contractor shall accomplish integration testing using questions from this database to ensure changes do not adversely affect system operation.

This information shall be provided in the FCA documentation. (CDRL A005, Design Review Data Package, DI-ILSS-81335)

4.5.8 The Contractor shall implement a verification program that ensures traceability of requirements from the Requirements Analysis phase of development through system implementation. The Contractor shall implement a validation program that includes Unit, Integration, and Formal Acceptance Testing as well as detailed test plans that permit effective tracking of requirements into the design and functionality of the completed solution and provide procedures for identification and correction of problems encountered during testing. To document system changes a Software Version Document shall be provided to the Government along with a copy of the Computer Software Product. Formal Acceptance Testing forms are signed by Government PM. (CDRL A00F, Software Version Document, DI-IPSC-81442A;

CDRL A00G, Computer Software Product, DI-IPSC-81488)

4.6 Logistics Support

4.6.1 The Contractor shall provide Logistician(s)/Systems Analyst(s) who possess current knowledge of the ALMSS operational baseline and User Manual and who can provide technical expertise to perform hands-on assistance, procedural guidance, and information analysis for system users and managers.

4.6.2 The Contractor shall initially respond to a Government request for assistance within 2 business days. Follow-up assistance, if required, shall be provided by a suspense date acceptable to the Government.

4.6.3 The Contractor shall support the End-of-Fiscal Year close-out team in identifying requirements and recommendations for funding. The Contractor shall also develop queries identifying usage and stock objectives and provide other data assistance as requested by the Government.

4.6.4 The Contractor shall support the Contingency Processing Team (CPT), whose purpose is to establish and/or provide support during unscheduled, prolonged downtime of supported systems.

4.6.5 The Contractor shall support Requirements Computations Data Administration by updating the Price Indices tables on an annual basis, researching and documenting any errors attributed to ALMSS computation module errors. The Contractor shall update the manual account SRAN numbers on a monthly basis and, prior to processing, verify Application Program Data, Quantity Per End Item, and Raw Program data with C2ISR Division Item Managers.

4.7 Training Support

4.7.1 The Contractor shall provide training materials for all logistics activity (i.e., supported systems, related application programs and equipment) to C2ISR Division personnel and system users. Training may include on-the-job assistance and/or classroom training. The Government

PR: FD2399-17-00129 PWS REVISION: 0 18

reserves the right to have training performed in a Government facility. Classroom training for remote system users shall be conducted at a location determined by the Government PM.

Training shall be provided to all users for new capabilities, including but not limited to, multiple Contractor sites and OLs. Locations for training related to Special Projects shall be provided by the SPPO. The Contractor shall coordinate training actions with the Government.

4.7.2 The Contractor shall provide experienced system analysts/logisticians who have current knowledge of ALMSS, the CUG networks and other supported systems within the C2ISR Division weapon system support infrastructures. Instructors shall have current knowledge of the C2ISR Division specific logistics and mission support requirements and applications. The Contractor shall review training courses and user documentation, identifying improvements and updating training materials.

4.7.3 The Contractor shall maintain and update project documentation, including supported system documentation as required, to reflect current operations and infrastructure.

4.8 Inventory Support

4.8.1 The Contractor shall provide personnel to perform all tasks associated with Inventory Control activities for C2ISR Division items as assigned.

4.8.2 The Contractor shall provide personal protective equipment for its employees in accordance with applicable Occupational Safety and Health Administration (OSHA) safety requirements and those spelled out in OSHA 3220-10N 2004, Worker Safety Series Warehousing.

4.9 Quality Assurance Provisions. The Contractor shall perform a Product and Process Quality Assurance (PPQA) function to verify and assure that baseline software requirements and software-related products for supported systems meet requirements. (CDRL A007, Process and Product Quality Assurance Plan, DI-CMAN-80789)

4.10 Configuration Management (CM) Plan. The Contractor shall maintain a CM function that controls and manages baseline software requirements for supported systems and software.

The Contractor shall ensure its CM function complies with standard requirements contained in the accredited organizational procedures. (CDRL A008, Configuration Management Plan, DI-

SESS-80858C)

4.11 Program Management Plan (PMP). The Contractor shall submit a draft PMP with the proposal, describing its approach to project organization execution and a summary of key…