PWS.pdf

PR: FD2060-15-90953 PWS 1

Performance-based Work Statement (PWS) Program Title: PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

CONTRACT LOGISTICS SUPPORT (CLS) AND

PRODUCTION OF THE

DEFENSE INJECTION/RECEPTION EMERGENCY ACTION

MESSAGE (EAM) COMMAND AND CONTROL (C2)

TERMINAL (DIRECT)/DIRECT-LIMITED INJECTION

TERMINAL (DIRECT-LITE) AND ALTERNATE INJECTION

TERMINAL (AIT)

Purchase Request #: FD2060-15-90953

Date; Revision #: 27 May 16, V3, PWS

PR: FD2060-15-90953 PWS 2

1.0 Description of Services

1.1 Objective(s): This Performance-based Work Statement (PWS) is to procure Contract Logistics Support (CLS) and Production for the Defense Injection/Reception Emergency Action Message (EAM) Command and Control (C2) Terminal (DIRECT), DIRECT-Limited Terminal Equipment (DIRECT-LITE) and Alternate Injection Terminal (AIT) with a Period of Performance (POP) of five (5) years (one 12-month basic with four ordering periods).

Throughout this PWS it should be understood that this entire PWS for CLS and Production is for DIRECT, DIRECT-LITE and AIT as applicable. The follow-on CLS effort is targeted to start 1 Jan 17. The overall contract type for this CLS is Firm Fixed Price (FFP), with Cost Plus Fixed Fee (CPFF) and Cost Reimbursable No Fee (CRNF); CPFF CLINs shall be utilized only in support of on-site DIRECT Maintenance Representatives (DMR’s), CRNF shall be utilized only in support of Travel and Per Diem. The contract type for Production is Firm Fixed Price (FFP) and Cost Reimbursable No Fee (CRNF) where CRNF shall be utilized only in support of Travel and Per Diem.

The CLS effort requires the Contractor to provide on-site management coverage, software updates, logistics, support the Government’s Information Assurance (IA) program, field support, and Engineering services. On-site management coverage includes removal & replacement (R&R), repairs of failed units, and on-site support. The Contractor shall repair items to serviceable condition to the latest hardware/software configuration approved and funded by the Government for that item. The Contractor shall provide CLS coverage/ services supporting additional sites once Production installations have been accomplished.

The CLS support to the new sites shall be added scope under the appropriate CLS CLINs.

Each Production effort includes the production and installation of a new system (either fixed DIRECT, DIRECT-LITE or AIT systems) into operational sites/platforms. Production entails the parts procurement, manufacture, assembly, inspection, and acceptance testing of the Prime Mission Equipment (PME) IAW the latest system configuration approved by the Government, and associated kits and spares. Installation includes detailed planning, site coordination, packaging and transportation, on-site installation and checkout and system activation. Other production tasks and supporting documentation include ancillary activities, informal and formal testing, and training includes Operator, Site Administer, and Maintenance training, as required. The Production culminates with the installation, demonstration of interoperability among DIRECT, DIRECT-LITE and AIT systems, and demonstration of interoperability with each specified Communication System.

PR: FD2060-15-90953 PWS 3

1.1.1 Background: DIRECT provides an automated capability to compose, transmit, receive, process, readdress, and acknowledge Emergency Action Messages (EAMs), Emergency Action Support Messages (EASMs), and non-Emergency Action Messages (non-EAMs) on all available EAM communication systems with expansion for future growth. DIRECT-LITE and AIT provides these same capabilities on a single EAM communication system.

1.2 Benefit to United States Air Force (USAF). This acquisition will benefit USAF by ensuring continued availability of the DIRECT the Prime Mission Equipment (PME). The DIRECT PME is comprised of all required system hardware, software and data to be installed at a specific site/platform to permit DIRECT, DIRECT-LITE and/or AIT to perform all of its critical functions. The PME includes all required common, site-peculiar, and Communication System-peculiar hardware, software, and data for a site or platform.

PR: FD2060-15-90953 PWS 4

2.0 Services Summary

Performance Objective PWS Reference

Performance Threshold

Follow-on Contract Logistics Support (CLS) and Production services

4.3.5 4.1.3 4.1.4

CLS repair of all serviceable items shall be to repair and bring back to serviceable condition within the established turnaround time of 45 calendar days, production is 18 months ARO, and shall be tracked and System Engineer/ Program Manager shall be informed of 100% of all configuration changes.

(CAV-AF) Reporting 4.19 The Contractor shall report production status using CAV-AF. The Contractor shall provide data on the actions conducted for each unit.

The Contractor shall report as actions occur.

Completion of Block Cycle

4.3.2 All PTRs scheduled for a Block Update must be

addressed and all required testing completed within the allowed block cycle time period, unless relief for one or more PTRs is granted by the DSSWG and/or the Government PM.

System Operational Availability (Ao)

4.3.12 4.11.1

Maintain system’s Ao of .999 as defined by the

DIRECT ORD.

Submission of Engineering Change Proposal (ECP)

4.2.6 All Class 1 changes to the baseline

configuration shall be submitted via ECPs to AFLCMC/WNYEDA. The contractor shall notify the WR-ALC Systems Engineer of all Class 2 changes, including all substitute parts changes, through Document Change Notices (DCNs).

Quality of data/document 4.1 - 4.14 There shall be no more than _5__ rejection(s) of data/document(s) per contract year. There shall be no more than one rejection of each data/document. The Government will reject the submitted data/document if __3__ or more technical errors or _5___ or more minor errors are found within the data/document. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is defined as a typographical or grammatical error.

The rejected data/document shall be corrected and resubmitted within __14__ business days of notification of Government rejection.

PR: FD2060-15-90953 PWS 5

Performance Objective PWS Reference

Performance Threshold

Receipt of data/document 4.1 - 4.14 There shall be no more than _3___ late submission(s) of data/document(s) per contract year. 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.

Request(s) for assistance 4.6 24-hour, 7-day help desk service shall be available for EA operators and on-site service technicians. Follow-up assistance, if required, shall be provided by a mutually agreed to suspense date acceptable to the Government.

Program Managemnt Services

4.3.1 4.3.9.1

The Contractor shall report program status quarterly

The Contractor shall provide support in program management to conduct and administratively support two (2) PMRs per year with proposed agenda delivery not less than 10 business days prior

Contractor personnel qualifications

4.3.2.6 Contractor personnel shall meet, at a minimum, Software Engineering Institute Capability Maturity Model rating of Level 3 or higher

3.0 Government Property and Services: The information contained in this section is not intended to be all inclusive or to detract from procedures outlined in specifications and other directives listed in Appendix B of this PWS.

a) The Contractor facilities shall be environmentally controlled to the extent deemed necessary by the contractor to ensure a quality product that meets the requirements specified in this PWS. Contractor furnished material or parts procured for replacement of unavailable material or parts shall equal or exceed the quality of the original material or parts. The material or parts shall be entirely suitable for build of the end item for its intended purposes.

b) Configuration changes may drive Contract Line Item Number (CLIN) additions and/or deletions and shall be mutually agreed to between the Government and Contractor. Functional capabilities shall not be changed, modified, or altered EXCEPT when an ECP has been submitted by the Contractor and approved by the Government.

c) Installation applicable to this contract shall be performed by contractor-provided personnel with the proper security clearance working in TOP SECRET/NC2-ESI facilities.

PR: FD2060-15-90953 PWS 6

d) The Software effort applicable to this contract must take place in a TOP SECRET environment with appropriately cleared personnel.

e) The Contractor Program Management shall be the interface between the support organizations, subcontractors, and the Government Program Office.

3.1 Contractor Responsibility: 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 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 site. http://farsite.hill.af.mil

3.2 Government Property to be Provided: The Government will transfer all GFE/GFP/GFI under contract FA8540-12-C-0008 to this new contract upon award.

3.3 Loss of Government Property

3.3.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 (BER). 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.3.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 the site below. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

http://www.dcma.mil/aboutetools.cfm

3.4 Return 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 Procuring Contracting Officer (PCO). All Department of Defense (DD) Form 1423 Contract Data Requirements List (CDRL) deliverables become the property of the Government upon receipt.

http://farsite.hill.af.mil/ http://www.dcma.mil/aboutetools.cfm

PR: FD2060-15-90953 PWS 7

3.5 Government System(s): The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/order. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the system account(s) will be closed.

4.0 CLS and Production Technical Requirements

This section provides detailed information for CLS and Production of the Systems. The information contained in this section is not intended to be all inclusive nor to detract from procedures outlined in specifications and other directives in this PWS. Workmanship shall be in accordance with the standard operating procedures and acceptance criteria in accordance with standard industry practice and those used by the Contractor.

a) The repair facilities shall be environmentally controlled to the extent deemed necessary by the Contractor to ensure the quality requirements specified in this PWS are met. The extent of repair required to return an item to a serviceable condition shall be determined by the inspection, test, bench check, and required disassembly.

Items input for repair shall be in a wide range of conditions, consisting of but not limited to:

• Pre-production unit

• Engineering Manufacturing Development (EMD)

• Items which are beyond the ability of field level skill to repair

• Items received which may vary in age and condition.

b) Contractor furnished material or parts used for replacement shall equal or exceed the quality of the original material or parts. The material or parts shall be entirely suitable for restoration of the end item for its intended purposes.

c) The Contractor shall provide repair services for all system items. National Stock Numbers (NSNs) and Part Numbers are subject to change as the baseline changes at the system level. Such configuration changes may drive Contract Line Item Number (CLIN) additions and/or deletions. Functional capabilities changes, modifications, or alterations shall only occur when an ECP has been submitted by the Contractor and approved by the Government. The Contractor shall repair items to serviceable condition to the latest hardware/software configuration approved and funded by the Government.

d) DIRECT, DIRECT-LITE and AIT consists of both commercial-off-the-shelf (COTS) equipment and newly designed/developed equipment. DIRECT utilizes a two-level maintenance concept; organizational and depot. Organizational-level hardware maintenance shall be performed by Contractor with the appropriate security clearance provided on-site Contractor/technicians are working in TOP SECRET/SCI/NC2-ESI facilities. Organizational-level hardware maintenance shall consist of system restoration by fault verification/isolation, removal/replacement of the faulty Line Replaceable Units (LRU), and functional checkout using existing technical manuals and other technical data. The Contractor shall, under the CPFF CLIN, have on-site maintenance technicians with the appropriate security clearance in place at NORTHCOM, PACOM, EUCOM, SITE-R, STRATCOM and NMCC. The Government will issue CAC Cards to Contractor personnel as required in order to ensure CONUS and OCONUS accessibility to multiple DOD facilities at system/site locations. Organizational-level maintenance at other sites will be performed by

PR: FD2060-15-90953 PWS 8

Government maintenance personnel, such personnel must have been trained by the Contractor.

e) For newly designed equipment, depot-level hardware maintenance shall consist of diagnostic analysis. Depot-level hardware maintenance shall use common support equipment and available technical data, for returned LRUs to isolate faulty Shop Replaceable Units (SRUs), the removal and replacement of faulty SRUs, and functional checkout. SRUs in most instances shall consist of circuit cards, power supplies, or fiber optics transmitters/receivers. The Contractor shall determine the most cost effective means of repair for each COTS hardware item consistent with meeting required system performance criteria and availability of technical data and spares.

f) Software maintenance shall consist of periodic updates (two (2) per year) to implement changes to NC2-ESI plans, to correct other system problems and to incorporate system enhancements. An Emergency Software update that must be released out of cycle, other than within the current software maintenance schedule, must be authorized by the Government Program Office and Joint Staff representative.

The Contractor shall, if needed, perform one (1) Emergency Software release per year.

Software maintenance will take place in a TOP SECRET environment by Contractor personnel with the appropriate security clearance. At the present time, the NC2-ESI access granting official has chosen to disallow NC2-ESI access for foreign nationals.

This precludes foreign nationals from working on the software or in on-site maintenance positions.

g) The Contractor Program Management function shall provide the interface between the support organization, subcontractors, and the Government Program Office.

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: The period of performance (POP) shall be 12-month for each CLS ordering period. There are five (5) CLS ordering periods. These ordering periods shall be exercised consecutively with no break in performance. Production will be performed in conjunction with CLS. The POP for each Production order shall be 18-month. The Production order shall be awarded during an on-going CLS ordering period on contract. The first Production order is to be awarded during the first CLS ordering period.

4.1.2 Place of Performance: These services shall be performed at the Contractor facility with the appropriate clearance-level and a combination of U.S. Government installations (specific installation names/locations are classified).

4.1.3 System Production: Facility and communication modification kits and initial spares in the quantity ordered shall be produced and acceptance tested. Fixed DIRECT and AIT systems will be installed and acceptance tested at the designated operational site(s). DIRECT- LITE systems may either be acceptance tested at the Contractor’s facility, or at the point of installation.

PR: FD2060-15-90953 PWS 9

4.1.5 Production Hardware: The Prime Mission Equipment (PME) is comprised of all system hardware, software, and data required to be installed at a specific site to ensure performance of all of its critical functions at that site or platform. The PME includes all common, site-peculiar, and Communication System-peculiar hardware, software, and data required for a site or platform.

4.1.5.1 Prime Mission Equipment: The composition of a system at a specific site depends on the number and types of workstations required to support the Command Center’s/ Platform’s operational procedures, the numbers and types of communication systems, and the site-specific database required to characterize the site configuration. The system shall meet the requirements of ESC DIR 1 and the Configuration Item Development Specification (CIDS), ESC DIR 106. The Contractor shall update the Installation Plan to reflect the system configuration at the time of installation for each site.

4.1.5.2 Facility Modification Kits: The composition of the site-specific Facility Modification Kit for each site/platform is defined in the Site Preparation Requirements and Installation Plan for each site. The Facility Mod Kit accommodates differences in the interfaces to site-provided support systems and the interfaces to the communication systems. The Contractor shall update this plan to reflect the Facility Mod Kit composition prior to the site installation.

4.1.5.3 Communication System Modification Kits: The composition of communication system-specific Communication System Modification Kits (Comm Mod Kits) is defined for each site in the ICD for each Communication System. These Mod Kits include any changes required to the Communication System side of the interface with DIRECT, DIRECT-LITE and/or AIT. Since a specific Communication System can have different interfaces at different sites, there can be more than one Comm Mod Kit type for a specific Communication System.

4.1.6 Obsolete Parts: The Contractor shall notify the government of parts and/or equipment required for production that has become obsolete and make recommendations to address the issue. This may require the substitution of a similar component or piece of equipment that is physically and functionally equivalent to the original part. A portion or portions of a printed wiring assembly (PWA) may need to be redesigned and a new layout for the assembly produced. Replacement parts or re-design shall be recommended to minimize impact and assure backward compatibility. There are two types of obsolete parts: Anticipated Obsolete Parts and Unanticipated Obsolete Parts. Replacement parts or re-design for unanticipated obsolete parts will be addressed under Over and Above CLIN as added scope.

4.1.4 Reserved.

4.1.7 Production Software

4.1.7.1 Software Block Updates: Block updates will be provided under the Contractor Logistics Support (CLS) portion of this contract to include all testing of production systems and shall use the most recent block updates.

PR: FD2060-15-90953 PWS 10

4.1.6.1 Anticipated Obsolete Parts: There are two types of anticipated obsolete parts:

a) Parts identified as obsolete in response to Government’s RFP/Pricing Request:

Parts, components, or assemblies identified as obsolete when the response to the Government’s RFP/pricing request for a Production option is generated. These replacement parts, components, or assemblies shall be integrated and delivered as part of the Production Equipment suite.

b) Parts Being Replaced under Tech Refresh: Parts, components, or assemblies undergoing Tech Refresh when the response to the Government’s RFP/pricing request for the Production option is generated. These replacement parts, components, or assemblies shall be integrated and delivered as part of the Production Equipment suite IAW the Tech Refresh fielding schedule. In the event that the Production Equipment is to be delivered and installed before the Tech Refresh is fielded, the equivalent old parts, component, or assemblies from the Depot spare shall be used as a temporary configuration.

4.1.6.2 Unanticipated Obsolete Parts: Unanticipated Obsolete Parts are defined as obsolete parts not identified in 4.1.6.1.

PR: FD2060-15-90953 PWS 11

4.1.7.2 Production Software Updates: Software changes required as a result of system production, installation, improvements and upgrades shall be performed as a part of this contract. Software and database changes as directed by Joint Chiefs of Staff (JCS) for OPLAN 801X revisions/updates in accordance with the CJCS Emergency Action Procedures (EAP) documents CJCSI 6811.01, DoD 5200.16, NSA FSRS No. 96-02, AFSPC (USAF)

006-95-I/II, CJCSI 3231.01, ACP 128, ESC-DIR-01, ESC-DIR-106, ESC-DIR-118-02400,

and ESC-DIR-118-02200. Software changes as a result of unanticipated obsolete parts shall be performed under Over and Above CLIN as added scope.

4.1.7.3 Evaluations: The Contractor shall assist the SPO in identifying, documenting, assessing, prioritizing and developing alternative approaches to resolving software issues as they may apply to this contract. Software issues can be identified by the user community, GDC4S, and the SPO.

4.1.7.4 Production Testing and Approval: New software shall successfully complete interoperability testing and receive Government approval of all related documentation. The Contractor shall perform and document any new software development in accordance with the following documents: MIL-STD-498, MIL-STD-973 and ESC-DIR-116. The Contractor shall perform interoperability developmental testing and shall fix any Trouble Reports (TRs) identified as a result of the test effort. In addition, the Contractor shall support any Government test activity associated with required field level operation testing. Support is through telephone, FQT, Template Review and DSSWG as required.

4.1.7.5 Documentation: The Contractor shall update the current program baseline documentation, as required, and incorporate and distribute the changes as required in accordance with the CDRL.

a) The Contractor shall update security documentation, incorporate and distribute changes in accordance with the CDRL whenever hardware or software security provisions are modified.

(CDRL A00F, DI-MISC-80841, Security Vulnerability Analysis, CDRL A00G, DI-MISC-81762, Security Evaluation Document (SED) CDRL A00X, DI-TMSS-81352, Trusted Facility Manual)

b) The Contractor shall possess and maintain a Software Engineering Institute Capability Maturity Model rating of Level 3 or higher. Also the Contractor shall maintain software using procedures and plans defined in the CRLCMP as guidance and provide quarterly metrics on cost, schedule and quality. The quarterly metrics are defined as PTR Status, Open vs. Closed PTRs, Cumulative Number of AIs and PTRs per phase, Software Line of Code (SLOC), Defects and Enhancements.

c) The Contractor shall update as required the set of FQT Test Procedure Sheets (TPSs), Message Generator/Receiver (MGR), test support command and data files, and Protocol Analyzer test scripts and other support files.

d) The Contractor shall maintain contract documentation in accordance with the terms and conditions of this CLS contract.

PR: FD2060-15-90953 PWS 12

4.1.8 Test Support Equipment: The Test Support Equipment (TSE) is comprised of the MGR and any other PSE required. TSE may be required to support informal testing, formal testing, installation and checkout, and/or one or more of the maintenance capabilities. The Contractor shall plan to re-use TSE to support more than one of these activities where practical.

4.1.9 Spares

4.1.9.1 Production of Spares: Each production run for PME shall include sufficient spares to support in-plant testing, installation and checkout. Sufficient spares shall be included to meet the requirement for on-site spares and to supplement the depot spares, as required.

4.1.9.2 Spares Management Support: At any site where a new production system is installed, the contractor shall provide the normal complement of spares.

a) Central depot management of spares shall be provided as a part of this contract.

This includes warehousing of depot spares stock, shipment of spares from the central depot warehouse to the operational sites, management of spares, shipment between sites, tracking of spares usage, and advising the Government of replenishment spares requirements.

4.1.10 MSG Vendor Support: The Contractor shall provide vendor support, as needed for the MSG and AIT software. This shall consist of establishing support agreements and/or service contracts for technical coordination as required to adequately define and resolve software problems. Provide a test configuration and any required support for recertification testing of the MSG and for integrated DIRECT/DIRECT-LITE/AIT in-plant testing.

4.1.11 Parts Approval Request: Nonstandard parts, defined as parts not specified in the current drawing set and that are non-Mil-Standard or commercial equivalent that are used in production must be approved by AFLCMC/WNYEDA via submittal of DI-MISC-80071E, as required.

(CDRL A00H, DI-MISC-80071E, Parts Approval Request)

4.1.12 Accessory and Component Reuse, Repair and Replacement: Parts/components of an end item determined defective during the production cycle shall be replaced with the same or equivalent serviceable parts. Contractor furnished material or parts procured for replacement shall equal or exceed the quality of the original material or parts.

4.1.13 Alert/Safe-Alert Reports: The Contractor shall submit all appropriate data requirements to the Government Industry Data Exchange Program (GIDEP) as it is generated.

The Contractor shall screen each Alert or Safe received from GIDEP to determine if the device or process for which the Alert is issued, is used in the manufacture of the unit and take appropriate action. The Contractor shall adhere to the policies and directives of GIDEP.

(CDRL A00J, DI-QCIC-80125B, GIDEP Alert Response, 1368128836C Highlight

1368128836C Highlight

PR: FD2060-15-90953 PWS 13

CDRL A00V, DI-QCIC-80126B, GIDEP Alert/Safe-Alert Report)

4.2 Control Data Requirement and Mandatory Regulations Data - Reports IAW DD 1423s and mandatory regulations as cited below:

4.2.1 Status Report: For the term(s) of the exercised basic contract and ordering period(s), the Contractor shall maintain a history of repair data and services for the DIRECT/DIRECT- LITE/AIT system, in contractor format. CDRL A001 and DI-MGMT-80368A list the requirements necessary for these quarterly status reports.

(CDRL A001, DI-MGMT-80368A, Status Report)

4.2.2 Software Version Description (SVD): The Contractor shall document, update, and submit a SVD to the Government upon completion of each final Block Cycle Change (BCC).

(CDRL A002, DI-IPSC-81442A, Software Version Description)

4.2.3 System Requirements Document (SRD): The SRD describes the top-level requirements for the DIRECT/DIRECT-LITE/AIT systems. Any changes to the SRD shall be documented and delivered to the Government at the end of the effort.

(CDRL A00Y, DI-IPSC-81431A, System Requirements Document)

4.2.4 Reserved.

4.2.5 Reserved.

4.2.6 Engineering Change Proposal (ECP): The Contractor shall submit Class 1 ECP for all changes to the baseline configuration. The ECPs submitted shall be technically accurate, complete, clearly written, and systematically account for the proposed configuration changes.

The Contractor shall notify the Government of all Class 2 changes, including all substitute parts changes, through Document Change Notices (DCN).

(CDRL A003, DI-CMAN-80639C, Engineering Change Proposal)

4.2.7 Interface Control Document (ICD): The Contractor shall document, update, and submit any changes to the ICD.

(CDRL A004, DI-CMAN-81248A, Interface Control Document)

4.2.8 Test Procedures: The Contractor shall provide test procedures for any software testing performed as part of this effort.

(CDRL A00A, DI-IPSC-81439A, Software Test Description)

1368128836C Highlight

PR: FD2060-15-90953 PWS 14

4.2.9 Test/Inspection Report: The Contractor shall deliver test/inspection reports that result from any testing performed as part of this effort. The inspections and tests shall be conducted by the Contractor and may be witnessed by designated Government representatives. The calibration standards for calibrating the test equipment shall be traceable to the National Institute of Standard Technology (NIST) IAW NIST SP250.

(CDRL A00M, DI-NDTI-80809B, Test/Inspection Report)

4.2.10 DoD Information Assurance Certification and Accreditation Process (DIACAP) Comprehensive Package/Risk Management Framework (RMF): The Contractor shall support the Government IAM by providing necessary information required to update and complete the DIACAP/RMF Comprehensive Package.

4.2.11 Reports/Records of Meetings/Minutes: The Contractor shall provide reports/records of meetings as required.

(CDRL A007, DI-ADMN-81505, Reports/Records of Meetings/Minutes)

4.3 Specific Work requirements

4.3.1 Program Management: The Contractor shall provide internal management and control from conception to final completion on all matters related to this PWS. A Program Manager (PM) shall be designated to serve as the Contractor focal point for the Government and shall ensure successful fulfillment of all PWS requirements within the agreed upon schedule. The Contractor PM shall report program status quarterly in accordance with contract requirements.

The report shall include milestone/task status, future plans, contract delivery status, and report preparer as defined in DI-MGMT-80368A.

(CDRL A001, DI-MGMT-80368A, Status Reports)

4.3.2 Software BCC Requirements: The Contractor shall accomplish, test and deliver two (2) scheduled block updates per year to the operational sites and to the DIRECT Software Support Facility (DSSF) at approximately six month intervals. Software updates shall include changes required to EAM templates, addresses, etc., in support of the new triad of conventional, nuclear, and Special Forces.

a) The content of each Software update shall be as determined by the DIRECT Software Support Working Group (DSSWG) and additional changes that are coordinated and established through the Program Office. Software updates shall be accomplished using processes and procedures described in the DIRECT Computer Resources Life Cycle Management Plan (CRLCMP) as guidance (one

(1) Energency per year if required).

b) The Contractor shall update the Operations Manual with each software update.

The Organizational Maintenance Manual shall be updated each time there is a change to the hardware baseline. A SVD shall be delivered with each software update. Affected Manuals, specifications and other documentation may be

1067478106E Sticky Note Accepted set by 1067478106E

1067478106E Highlight

PR: FD2060-15-90953 PWS 15

updated in redline format at the time of each software or hardware update.

Updated final documents shall be delivered in accordance with applicable CDRLs.

The Contractor shall provide the appropriate training to EA operators with each software change as required.

(CDRL A002, DI-IPSC-81442A, Software Version Description CDRL A008, DI-IPSC-81443A, Software Users Manual CDRL A009, DI-IPSC-81440A, Software Test Report CDRL A00A, DI-IPSC-81439A, Software Test Description CDRL A00B, DI-IPSC-81441A, Software Product Specification CDRL A00C, DI-IPSC-81435A, Software Design Description CDRL A00U, TM-86-01D, Technical Manual Contract Requirements CDRL A003 DI-CMAN-80639C, Engineering Change Proposals CDRL A00D, DI-CMAN-80640C, Request for Deviation CDRL A00E, DI-CMAN-80643C, Specification Change Notice)

4.3.2.1 Acceptance Criteria: The Contractor shall ensure that all contractor-delivered products meet the following criteria for Government acceptance of software corrective changes, upgrades, and enhancements:

a) Successfully conduct Formal Qualification Test (FQT)/Regression Test.

b) No priority one or two (as defined by IEEE/EIA 12207.2 Annex J) problem reports open.

c) Changed, upgraded, or enhanced software is compliant with the documents specified in Section 4.3.2.5.1 of this PWS.

d) Government approval of the deliverables, to include documentation required for each block cycle.

(CDRL A009, DI-IPSC-81440A, Software Test Report, CDRL A00A, DI-IPSC-81439A, Software Test Description)

4.3.2.2 Technical Support: The Contractor shall provide technical support for diagnosing and resolving communications system interface problems associated with DIRECT. Any changes identified that affect interfaces to external systems shall be captured in the appropriate ICDs and the Interface Requirements Specification (IRS) in accordance with appropriate CDRLs.

(CDRL A004, DI-CMAN-81248A, Interface Control Document, CDRL A00L, DI-IPSC-81434A, Interface Requirements Specification)

a) The Contractor shall provide vendor support for the MSG and AIT software. The vendor support shall consist of establishing support agreements and/or service contracts to adequately define and resolve software problems. Provide a test configuration and any required support for DISA recertification testing of the MSG and for integrated DIRECT/DIRECT-LITE/AIT/MSG in-plant testing.

1067478106E Highlight

1067478106E

PR: FD2060-15-90953 PWS 16

4.3.2.3 Problem Report/Change Request Investigation: The Contractor shall investigate problem reports and change requests. The Contractor shall develop subsequent recommendations for change proposals. Recommendations shall include performance, schedule, and cost components.

(CDRL A003, DI-CMAN-80639C, Engineering Change Proposals)

4.3.2.4 Test Environment support: The Contractor shall provide and maintain a test environment capable of testing past, current, and future software configurations. The Contractor shall document and control the configuration of each test environment the contractor utilizes, to include but not be limited to all elements of equipment, software, and human or automated processes present in each test environment.

a) The Contractor shall maintain a factory test bed/development environment for support and developmental testing of the DIRECT/DIRECT-LITE/AIT systems.

The test bed will be located at the Contractor facility and shall be capable of supporting a wide range of efforts including Factory Acceptance Testing (FAT), factory training in operation and maintenance, software security scans and accreditation, formal test program support (i.e., supporting Air Force System Interoperability Testing, Joint Interoperability Testing, and Operational Testing as directed by the SPO). Live communications are not required for this Test Bed.

(CDRL A005, DI-QCIC-880154, Installation and Acceptance Test Plan (IATP), CDRL A006, DI-QCIC-80512, Installation Test Report (ITR))

4.3.2.5 Software Maintenance and Update: The Contractor shall make corrective changes, improvements, or upgrades to the software on an as needed basis as directed by the Government in order to:

a) Correct identified defects and deficiencies

b) Improve performance or other attributes, or adapt the software to a modified environment

c) Incorporate new technologies, functionalities, and security upgrades

4.3.2.5.1 Software Updates: The Contractor shall design/modify requirements and incorporate software and database changes as directed by Joint Chiefs of Staff (JCS) for OPLAN 801X revisions/updates in accordance with the CJCS Emergency Action Procedures (EAP) documents CJCSI 6811.01, DoDS 5200.16, NSA FSRS No. 96-02, AFSPC (USAF)

006-95-I/II, CJCSI 3231.01, ACP 128, ESC-DIR-01, ESC-DIR-106, ESC-DIR-118-02400,

ESC-DIR-118-02200, participate in EAP conferences and other planning activities and document and track changes in accordance with procedures described in the CRLCMP as guidance.

PR: FD2060-15-90953 PWS 17

a) The Contractor shall perform and document emergency software updates up to one (1) per year, if required. Emergency changes shall be accomplished as required using procedures documented in the CRLCMP as guidance.

b) All current software build processes (e.g., Trusted Download Steps) that have been previously accepted by the Government will continue to be utilized and the processes will continue to be accepted.

(CDRL A002, DI-IPSC-81442A, Software Version Description, CDRL A008, DI-IPSC-81443A, Software Users Manual, CDRL A009, DI-IPSC-81440A, Software Test Report, CDRL A00A, DI-IPSC-81439A, Software Test Description, CDRL A00B, DI-IPSC-81441A, Software Product Specification, CDRL A00C, DI-IPSC-81435A, Software Design Description, CDRL A003, DI-CMAN-80639C, Engineering Change Proposals, CDRL A00D, DI-CMAN-80640C, Request for Deviation, CDRL A00E, DI-CMAN-80643C, Specification Change Notice)

4.3.2.5.2 Testing and Approval: New software shall successfully complete Interoperability Testing and receive Government approval of all related documentation. The Contractor shall perform and document any new software development in accordance with the following documents MIL-STD-498, MIL-STD-973 and ESC-DIR-116. The Contractor shall perform Interoperability Developmental Testing and shall fix any Trouble Reports (TRs) identified as a result of the developmental test effort. In addition, the Contractor shall support any Government test activity associated with required field level operational testing. Support is through telephone, FQT, Template Review and DSSWG as required.

4.3.2.6 Documentation/TR Fixes: The Contractor shall update and maintain applicable software documentation when affected by software maintenance/upgrade or enhancement delivery order efforts. The Contractor shall provide additional documentation when required for larger upgrade and enhancement delivery orders as directed by the government. The Contractor shall work with the Government to identify and fix hardware and software TRs.

The Contractor shall make corrections to include; updates to technical orders, drawing packages, and software documentation. The Contractor shall resolve all CAT I (Priority 1A through 1E) and CAT II Priority 2A & 2B software and hardware defects (per TO 00-35D- 54). Priorities 1A through 1C are considered Emergency Conditions; Priorities 1D through 2B are considered Urgent Conditions.

(CDRL A00C, DI-IPSC-81435A, Software Design Description)

a) The Contractor shall update the Software Transition Plan, if requested by the Government, in accordance with the applicable CDRL, to reflect current information and include planning information for transition of software support to a different facility at the conclusion of the contract.

(CDRL A00N, DI-IPSC-81429A, Software Transition Plan)

PR: FD2060-15-90953 PWS 18

b) The Contractor shall update ICDs and any other documentation as required to the current program baseline and incorporate and distribute changes as required in accordance with the CDRL and documents 00-1426901, 00-1426904, 00- 1426905, 00-1426908 and ESC-DIR-135C.

(CDRL A004, DI-CMAN-81248A, Interface Control Documents)

c) The Contractor shall update security documentation and incorporate and distribute changes in accordance with the CDRL whenever hardware or software security provisions are modified.

(CDRL A00F, DI-MISC-80841, Security Vulnerability Analysis, CDRL A00G, DI-MISC-81762, Security Evaluation Document (SED) CDRL A00X, DI-TMSS-81352, Trusted Facility Manual)

d) The Contractor shall possess and maintain a Software Engineering Institute Capability Maturity Model rating of Level 3 or higher, maintain software using procedures and plans defined in the CRLCMP as guidance and provide quarterly metrics on schedule and quality. The quarterly metric reporting requirement shall be met by providing the following metrics:

PTR Status Opened vs. Closed PTRs Cumulative Number of AIs and PTRs per Phase Software Lines Of Code (SLOC) Defects and Enhancements

e) Additionally, PTR status shall be sent to AFLCMC/WNYBBA periodically (e.g., monthly) via e-mail in order to report to the Government which PTRs are being worked for the next software release and to gain concurrence and approval of the PTRs.

f) The Contractor shall maintain and update as required the set of Formal Qualification Test (FQT) Test Procedure Sheets (TPSs), MG/R test support command and data files, and Protocol Analyzer test scripts and other support files.

g) The Contractor shall implement automated system requirements tracking and traceability tools and maintain databases required for these automated systems.

The Contractor shall maintain contract documentation in accordance with the terms and conditions of this contract. The contractor shall maintain the address database for DIRECT/DIRECT-LITE, MSG and AIT. Incorporate address database changes into regularly scheduled software updates. Government expectation is that the contractor shall maintain the IA baseline established at

CT&E.

(CDRL A00P, DI-IPSC-81437A, Database Design Description)

1067478106E Highlight

PR: FD2060-15-90953 PWS 19

4.3.2.7 Technical Report/Depot status Report: The Contractor shall establish and maintain a maintenance database of on-site maintenance actions (both corrective and preventive, including sufficient information to measure the respond/repair time for the call and corrective actions taken), depot maintenance activities, spares usage, and requests for assistance, to the help desk. Provide a quarterly report of all these maintenance activities to the SPO in accordance with the applicable CDRL.

(CDRL A00Z, DI-MISC-80508B, Technical Report)

4.3.3 Test: The Contractor shall support and participate in on-site acceptance testing at two sites in accordance with the CRLCMP for each update to the software. Usually, these sites are chosen during the DSSWGs and schedules finalized soon after. This testing shall include exercising new or modified capabilities using live communications between the two sites and regression testing as appropriate. Telephone participation is acceptable so long as the intent is met and requirement satisfied.

4.3.4 Manufacturing Management

4.3.4.1 Manufacturing Management System: The Contractor shall implement and maintain a manufacturing management system in accordance with its internal processes and ISO 9000 which ensure satisfaction of the system requirements.

4.3.4.2 Long Lead Analysis: The Contractor shall analyze lead-times for subassemblies, components, and materials to assess the impact of such lead-time on anticipated production schedules. The Contractor shall brief the status of Long Lead items and/or problems through status reports and during reviews and PMRs.

4.3.5 Repair Services: The Contractor shall provide the necessary labor, materials, facilities and equipment required to analyze, troubleshoot, repair, overhaul and test assemblies, parts and the Operating System Software that are maintained or repaired under this contract. These services also include alignment, adjustment, calibration, testing, movement, storage and reporting status related services to the repair and return to the users. If an item cannot be repaired or replaced due to obsolescence then the Contractor shall provide written notice of such to the Government and the Contractor will be relieved from repairing/replacing the item.

4.3.5.1 Spares Management Support: Under the CLS CLINs, the Contractor shall perform on-site spares management and data management at sites where a contractor provided maintenance technician is available. These tasks shall be accomplished by the on-site maintenance technicians. Spares management shall consist of tracking the number of operational spares available at each site, packaging and arranging for the shipment of those failed LRUs which will be returned to the central depot, receiving spares shipped from the central depot, and turning failed classified equipment over to the designated Government representative for disposition.

1067478106E Highlight

PR: FD2060-15-90953 PWS 20

a) The contractor shall provide central depot management of spares. This shall include warehousing of depot spares stock, shipment of spares from the central depot warehouse to the operational sites, management of spares shipment between sites, tracking of spares usage, and advising the Government of replenishment spares requirements.

b) The contractor shall perform diagnostics of failed LRUs returned from the field and prepare cost estimates for repair of these units.

4.3.5.2 Critical Items: Critical items of any category shall be expedited to the extent possible, as directed by the Production Management Specialist (PMS) through the Procuring Contracting Officer (PCO).

4.3.5.3 Over and Above Repairs – Work Request

4.3.5.3.1 Authorization: Written authorization for repair of recoverable items not listed in the BEQ table, or for quantities of items over the BEQ table specifies quantities, or engineering services not identified included in the PWS must be received from AFLCMC/ WNYBBA through the PCO prior to commencement of required activity. Authorization to proceed will be provided by separately funded work request approved by the Administrative Contracting Officer

(ACO).

4.3.5.3.2 Engineering Services: It is recognized by the parties hereto that during the performance of this contract, engineering services and other system support not forecast, may be required hereunder, and shall be independently estimated and priced on a case-by-case basis. These activities may include, but are not limited to Engineering Services in support of:

a) System Analysis

b) Failure Analysis

c) Diminishing Source Problems

d) Improved Item Replacement

Program (IIRP)

e) R & M Improvements

f) Data Evaluation Analysis

g) Software Updates/Corrective

Maintenance (ECPs)

h) Deficiency Reports

4.3.6 Information Assurance: The Government DIRECT Program Manager is the lead agent for establishing, developing, maintaining, and documenting all aspects of the information assurance program. The Government DIRECT Information Assurance Manager (IAM) identifies, addresses, authorizes, approves, and reports on all IA related issues to the Certification Authority (CA) or Designated Accrediting Authority (DAA). The Government IAM is responsible for completing and maintaining the DIACAP/RMF certification package. The current Authority to Operate (ATO) is valid through Aug 16.

i) Site Relocations

j) Site Equipment Relocations

k) Site Surveys

l) CLS for New Sites Added via Production Orders

m) Replacement of Obsolete Parts under CLS

n) Replacement of Unanticipated Obsolete Parts under Production

o) Changes to the fielded systems based on the evaluation of TCNOs

PR: FD2060-15-90953 PWS 21

4.3.6.1 Contractor Responsibilities: The Contractor shall support the System IA Program by providing system design information, logic diagrams showing security boundaries, parts lists, and Con Ops information for DIRECT, DIRECT-LITE and AIT systems suitable for inclusion in the DIACAP/RMF package. The Contractor shall provide a Technical Write-up describing the functionality of DIRECT, DIRECT-LITE, MSG and AIT configurations as necessary. The Contractor shall create an unclassified build of the software and install it on the DSSF to support IA control testing. The Contractor shall provide access to the operating systems of the WSP, MP server, MSG, AIT and DIRECT-LITE laptop so that IA control tests can be run by the Government. The Contractor shall support the Government in running the IA control tests on the MP server, WSP, DIRECT-LITE, MSG and AIT platforms. The Contractor shall provide Security Analysis Reports and the Security CDRLs. The Security Analysis Reports shall consist of assessments of the security impact of each individual PTR that is implemented and fielded. The Security CDRLs shall consist of the Security Vulnerability Analysis (SVA), Trusted Facility Manual (TFM), and Security Evaluation Document (SED). The Contractor shall support the Government in reviewing the IA control test findings, provide technical justification for POA&Ms, waivers, or exemptions.

a) The Contractor shall obtain Program Office approval for the inclusion of all new third party software (e.g., open-source, freeware, mobile code, source code or binaries) and hardware (e.g, technical refresh) proposed for future system use prior to its use or integration.

b) The Contractor may be required to have one Systems Engineer and one Software Engineer travel to support Information Assurance meetings with the DIRECT PM and/or IAM. This travel will be no more than 1 trip per year, not to exceed 5 days.

4.3.6.2 Program…