Optic PWS _Final.docx

Performance Work Statement Optic Hardware / Software Sustainment for the Ground Based Air Defense Program Management Office

3 September 2021

Revision

Table of Contents

Introduction Program Manager (PM) for Ground Based Air Defense (GBAD) is responsible for the sustainment of the Advanced Man Portable Air Defense System (A-MANPADS) and the development, fielding and sustainment of the Marine Air Defense Integrated System (MADIS) Family of Systems (FoS), including Counter-Unmanned Aerial Systems (C-UAS) and Medium Range Intercept Capability (MRIC).

Scope of Work Work performed under this Performance Work Statement (PWS) will support the engineering efforts to develop, test, and deliver software products and services in support of the MADIS FoS for MADIS Increment 1, L-MADIS 0 –Mark 1 and Mark II, and E-MADIS.

Lifecycle Sustainment The Contractor shall perform lifecycle sustainment. Lifecycle sustainment includes Contractor delivery of new software licenses, performance of maintenance to include, but not limited to, software cybersecurity updates and support, delivery of fixes for issues and trouble reports (TR), development and integration of modifications or upgrades to add new functionality and capabilities, and performance of maintenance actions to correct system defects. Maintenance includes inspection, diagnosis, and repair of systems, subsystems and components. Additionally, lifecycle sustainment activities include Contractor actions needed to update or deliver documentation that supports the development, testing, installation, training, operations, security, and sustainment of the software applications and component repair. Included within the lifecycle sustainment activities is the underlying objective for effective program management and incorporation of commercial best practices and processes needed to effectively and efficiently execute projects.

Problem Change Request (PCR) Allocation The Contractor shall deliver two software builds to implement software changes through the test cycle. The test events and corresponding demand signal for the builds required is detailed below and intended to support the maturation of capabilities. The first build will be in support of Development Test (DT) 3 and will be allocated PCRs resulting from DT1 and DT2. The second build will be in support of DT5 and will be allocated PCRs resulting from DT3 and DT4.

The Contractor shall deliver MADIS 1.0 software to support the test schedule including System Integration Test (SIT) 1, 2, 3; System Verification Test (SVT) 1 and 2; Operational Assessment; and Initial Operational Test and Evaluation (IOT&E). Additionally, the Contractor shall support quarterly MADIS FoS software updates.

The assignment of and effort associated with TRs and Test Incident Reports (TIRs) is defined in sections 3.2.5 and 3.2.6.

Requirements The Contractor shall perform the work described in Sections 3.1 – 3.6 and provide the deliverables defined within the identified Contract Data Requirements List (CDRL) within the subsections.

Safeguarding Covered Defense Information and Cyber Incident Reporting

1. System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews

a) Within thirty (30) days of contract award, the Contractor shall make its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the Government at the contractor’s facility. The SSP(s) shall implement the security requirements in Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The Contractor shall fully cooperate in the Government’s review of the SSPs at the Contractor’s facility.

b) If the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012 then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government. The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

c) Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s) at the Contractor’s facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies in the SSP(s).

d) The Government may, in its sole discretion, conduct subsequent reviews at the Contractor’s site to verify the information in the SSP(s). The Government will conduct such reviews at least every three (3) years (measured from the date of contract award) and may conduct such reviews at any time upon thirty (30) days’ notice to the Contractor.

2. Compliance to NIST 800-171

a) The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1) (NIST SP 800-171), or establish a SSP(s) and POA&Ms that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.

b) Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and POA&M their plans to implement the following, at a minimum:

(1) Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

(2) Implement Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

(3) Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

(4) Audit user privileges on at least an annual basis;

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which shall be evaluated by the Navy for risk acceptance.

(7) Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

3. Cyber Incident Response:

a) The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

b) Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3) Instructions for Submitting Media available at http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions_for_Submitting_Me.... In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

c) If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

4. Naval Criminal Investigative Service (NCIS) Outreach The Contractor shall engage with NCIS industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting DON programs and technologies.

5. NCIS/Industry Monitoring

a) In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

b) If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractor.

c) In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non-US law.

2.2 Service Contract Reporting Requirements

Services Contract Reporting (SCR) requirements apply to this contract. The contractor shall report required SCR data fields using the SCR section of the System for Award Management (SAM) at following web address: https://sam.gov/SAM/.

Reporting inputs will be for the labor executed during the period of performance during each Government FY, which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://sam.gov/SAM/.”

2.3 Program Management

In support of GBAD efforts, the Contractor shall deliver a Monthly Status Report (MSR). The MSR shall provide an overall status of the contract. The MSRs delivered by the Contractor shall report cost, schedule, and performance and status of known risks, risk mitigation efforts. The MSR shall identify travel that occurred during the reporting period along with details of the work accomplished during the trip.

CDRL B004, Contractor’s Progress, Status and Management Report

2.4 Government Furnished Property (GFP) Management

If the Government provides GFP, the Contractor shall manage, control, use, preserve, protect, repair and maintain government property within its possession. The contractor shall initiate and maintain the processes, systems, procedures, records, and methodologies necessary for effective control of GFP. During the period of performance, the contractor shall disclose, in writing to the Contracting Officer Representative (COR), any significant changes to their property management system. The Contractor shall perform inventory of GFP and report GFP inventory monthly in accordance with CDRL B004. The Contractor shall be responsible for receipt, accountability, security, storage, and reporting requirements under those processes for the GFP provided.

GFP consists mostly of information technology and field support equipment that has been properly inspected, inventoried, reported and stored as per DoDI 4161.02: Accountability and Management of Government Contract Property.

The contractor shall inspect all inventory received, identify and report status to include any discrepancies or deficiencies to the Government in accordance with CDRL A006. The contractor shall be responsible for ensuring contractor personnel who transport any equipment in commercial vehicles are properly licensed and insured according to State laws and regulations.

The Contractor shall report GFP issues, maintenance and repair actions monthly in accordance with CDRL B004.

CDRL A006, Technical Report-Study/Services - Inventory / Discrepancies List CDRL B004, Contractor’s Progress, Status and Management Report – Monthly Status Report

2.5 Maintenance and Repair

The Contractor shall provide maintenance and repair services on components that are malfunctioning, broken, damaged, and not serviceable by a Field Service Representative. Where possible the Government will send component to the Contractor, if not possible the Contractor shall go to the location of the component to conduct aforementioned tasks. The Contractor shall prepare and provide a cost estimate to the COR for all required unscheduled maintenance actions with a cost above $2,000, prior to repair. Upon approval, unscheduled maintenance actions shall be performed and invoiced for the actual costs incurred and total man hours to perform the repairs. The Contractor shall provide a detailed invoice each time an item is charged to the unscheduled maintenance contract line item. The Contractor shall provide a detailed summary of the maintenance/repair actions at 50% completion; 75% completion and final analysis of the component at 100% completion. Repair Action Reports for 50% and 75% completions can be sent as an email overview; however, the Repair Action Report for 100% completion will require a formal delivery as a CDRL.

CDRL XXXX,

CONFIGURATION MANAGEMENT, CYBERSECURITY, SOFTWARE Development and DELIVERY Purpose The purpose of this section of the PWS is to define requirements and the processes which involve changes to the MADIS FoS software baseline; product documentation; system and software engineering artifacts; cybersecurity requirements, and the subsequent delivery of the associated software releases. MADIS FoS software will be required to change to meet several external factors (i.e. cybersecurity updates, Commercial off the Shelf (COTS) updates, enhancements, defect corrections). Therefore, the software baseline for MADIS Optic Computer Software Configuration Item (CSCI) will be reviewed and modified at scheduled times to meet timeframes for required changes that will be published as software releases. Changes shall be directed by the COR and coordinated with the GBAD CCB.

Configuration Management Configuration Management (CM) The Contractor shall follow and adhere to the CM procedures and policies outlined in the GBAD Configuration Management Plan (CMP). The Contractor shall follow a rigorous CM process that conforms to the GBAD CMP, MIL-HDBK-61A, and established Contractor CM processes. Any changes to hardware that changes configuration during maintenance shall be reported to GBAD to determine if the repair is significant enough to require an update in the part number which shall be identified at the 75% completion from paragraph 2.1.5.1.

Software Configuration Control The Contractor shall implement and maintain a Software Configuration Management (SCM) process for the MADIS Optic CSCI, providing baseline control of the MADIS Optic CSCI and software-related products.

Configuration Control Board (CCB) The Contractor shall support and participate in bi-weekly CCB meetings by participating as a non-voting member to the CCB. The Contractor may be required to participate in more frequent CCB meetings to address immediate issues between the scheduled bi-weekly CCB meetings. The Contractor services and contributions to the CCB shall focus on current GBAD optic hardware baselined equipment, and software TIRs and TRs submitted to the CCB. The Contractors shall also support CCB discussions regarding Engineering Change Proposals (ECPs) related to MADIS Optic CSCI software changes. The names of the Contractor primary and alternate CCB members shall be provided to the Government and will subsequently be designated as non-voting members in a CCB assignment letter from the Government.

Software Product Documentation Control The Contractor shall deliver commercial technical manuals, user guides, COTS Manuals and Associated Supplemental Data, and updated Software Version Descriptions (SVD) IAW CDRL A001. The contractor shall update these documents to reflect software changes made by the Contractor under this contract and deliver the documents IAW the applicable CDRL.

CDRL A001, Software Version Description (SVD)

Test Incident Report (TIR) Assignment The Contractor shall receive, investigate, and respond to TIRs, as directed by the GBAD CCB. The Contractor shall analyze TIRs to formulate technical recommendations. The Contractor’s analysis and/or recommendations shall be provided to the GBAD CCB for consideration and disposition.

Trouble Report (TR) Assignment The Contractor shall receive, investigate, and respond to TRs, as directed by the GBAD CCB. TRs may be associated to the software baseline and/or documentation. The GBAD Software Baseline Manager will schedule TRs for incorporation into software releases.

Software Release Process Software releases will be scheduled and defined by the GBAD Software Baseline Manager IAW GBAD CMP and build strategy on a quarterly order basis or as developmental testing schedules require.

Cycle of a Software Delivery The Contractor shall deliver software releases defined by the GBAD Software Baseline Manager. The typical cycle for a software release is described below.

Contractor Software Testing Software Test Procedures The Contractor shall maintain detailed Software Test Procedures for each Contractor Software Qualification Test (SQT). The test procedures shall define schedule, test site, personnel requirements, test assets required, automated test tools required, simulation tools required, need for Government assets, System/Subsystem Specification (SSS) requirements being tested IAW software testing practices outlined in IEEE/EIA 12207, and the Contractor’s analysis approach. Each test procedure will provide a pass/fail status for each requirement tested. The Government will provide the access to the Original Equipment Manufacturer’s baseline set of Software Test Procedures.

Software Ready for Test (SRFT) Review The Contractor shall conduct a Software Ready for Test (SRFT) Review prior to the start of each Optic CSCI Software Release SQT. The purpose of the Contractor SRFT is for the Contractor to conduct a formal review of their readiness to enter SQT. The Contractor and the Government shall mutually agree upon the format and agenda of this review. The Government reserves the right to attend all Contractor SRFTs.

Software Release Delivery The Contractor shall deliver software releases to support GBAD software TR resolution, software maintenance and other software updates in releases defined by the CCB. The software releases shall include the delivery of source code for non-commercial software developed as part of the GBAD program and include the following associated Software Release CDRLs:

CDRL A001, Software Version Description (SVD) CDRL A002, Test/Inspection Report/Contractor Test Report CDRL A003, Computer Software Product End Items CDRL E001, Commercial Off-The-Shelf (COTS) Manuals and Associated Supplemental Data

The Contractor shall perform the following for the Optic CSCI:

Source Code Audits If requested, the Contractor shall deliver the results of software code scans, as related to the GBAD Optic CSCI, in support of determining the compliance posture of the software.

CDRL A002, Test/Inspection Report/Contractor Test Report Post Award Conference The Contractor shall host and lead a Post Award Conference (PAC) within ten (10) calendar days of the start of performance. The Contractor shall schedule and conduct this meeting, in coordination with the COR. The purpose of the PAC is to: 1) discuss any unique characteristics of the requirement(s); 2) discuss any changes or updates from proposal; 3) identify stakeholders' roles and responsibilities; and 4) establish a common understanding of cost, schedule, and performance expectations. The contractor shall deliver the following:

CDRL A005 – Conference Agenda CDRL A006 – Conference Minutes

Contractor Performance Reviews

In support of PM GBAD efforts, the Contractor Program Manager shall attend and participate in the Contractor Performance Reviews to assess the Contractor’s performance during the reporting period. There shall be no more than four (4) reviews per contract year, which shall begin three (3) to four (4) months after contract award, and shall last less than 1 (one) hour. The reviews shall be conducted virtually. At these meetings, the COR will apprise the Contractor of how the Government views the Contractor’s performance and the Contractor shall apprise the Government of all concerns, if any, being experienced. The Government may take action to resolve these concerns as appropriate. The contractor shall deliver the following:

CDRL A005 – Conference Agenda CDRL A006 – Conference Minutes

TRAVEL

The contractor shall provide onsite engineering support at integration facilities and test events as directed by the GBAD COR. The contractor’s engineering and technical representatives may be required to perform analysis and or integration on site to support the analysis of or correction to PCRs.

During execution of this contract, the Contractor shall travel to support technical and management review meetings and test events.

(a) Performance under this contract may require travel by Contractor personnel. If travel, domestic or overseas is required, the Contractor is responsible for making all necessary arrangements for its personnel. These include but are not limited to medical examinations, immunizations, passports, and visas etc., and security clearances. Travel is anticipated, but not limited to Naval Surface Warfare Center (NSWC) Crane, IN; NSWC Dahlgren, VA; Marine Corps Air Station Yuma, AZ; and other Virginia locations.

(b) The Government will reimburse the Contractor for allowable travel costs incurred by the Contractor in performance of the contract in accordance with FAR subpart 31.2. Travel required for tasks assigned under this contract shall be governed in accordance with current Joint Travel Regulations (JTR) and Department of State Standardized Regulations (DSSR).

(c) Travel and subsistence are authorized for travel beyond a 50 mile radius of the Contractor’s office whenever this contract requires work to be accomplished at a temporary alternate worksite. No travel or subsistence shall be charged for work performed within a 50 mile radius of the Contractor’s office. The Contractor shall not be paid for travel or subsistence for personnel who reside in the metropolitan area in which the tasks are being performed. Travel performed for personal recreation or daily travel to and from work at the Contractor’s facility will not be reimbursed.

(d) The Contractor shall be paid on the basis of actual amount paid by the contractor to the extent that such travel is necessary for the performance of services under the contract and is authorized by the COR in writing, and subject to the cost principles in FAR 31.2 and other requirements noted subsection (b) above.

(e) The Contractor agrees, in the performance of necessary travel, to use the lowest cost mode commensurate with the requirements of the mission. When it is necessary to use air or rail travel, the Contractor agrees to use coach, tourist class, or similar accommodations to the extent consistent with the successful and economical accomplishment of the mission for which the travel is being performed.

(f) The Contractor’s invoices shall include receipts for expenses over $75.00 substantiating actual costs incurred for authorized travel.

(g) The Contractor shall be reimbursed for car rental, exclusive of mileage charges, as authorized in the basic contract or upon approval by the COR, when the services are required to be performed beyond the normal commuting distance from the Contractor’s facilities. Car rental for a team on temporary duty (TDY) at one site will be allowed for a minimum of four (4) persons per car, provided that such number or greater comprise the TDY team.

(h) The Contractor shall not be paid for per diem for Contractor personnel who reside in the metropolitan areas in which the tasks are being performed. Per diem shall not be paid on services performed within a 50 mile radius of the Contractor’s home office or the Contractor’s local office. Per diem is authorized for Contractor personnel beyond a 50 mile radius of the Contractor’s home or local offices whenever a task assigned requires work to be done at a temporary alternate worksite. Per diem shall be paid to the Contractor to the extent that overnight stay is necessary and authorized under this contract by the COR. The authorized per diem rate shall be the same as the prevailing per diem in the worksite locality. These rates will be based on rates contained in the JTR and DSSR. The applicable rate is authorized at a flat seventy-five (75%) percent on the day of departure from Contractor’s home or local office and on the day of return.

(i) Prior to incurring any travel expenses, the Contractor shall submit a travel request to the COR for prior approval. Trips not authorized by the COR will not be reimbursed. In addition, a travel template shall be completed at the conclusion of each trip and submitted with the invoice and receipts after costs are incurred.

OTHER DIRECT COSTS

During execution of this PWS, the Government does not anticipate Other Direct Costs (ODCs). If ODCs are identified, all ODCs and timelines for support shall be identified to the GBAD COR by the Contractor, and a cost estimate to support the events shall be provided by the Contractor and approved by the COR prior to purchase.

SECURITY REQUIREMENTS

This contract will require the contractor to have a Secret Facility Clearance and will require certain contractors to obtain and maintain classified access eligibility. The contractor shall have a valid Secret Facility Clearance and a Secret Safeguarding Level prior to classified performance at the contractor’s facility. The prime contractor and all sub-contractors (through the prime contractor) shall adhere to all aspects of 32 CFR Part 117 NISPOM and DoD Manual 5220.22 Volume 2. All personnel identified to perform on this contract shall maintain compliance with Department of Defense, Department of the Navy, and Marine Corps Information and Personnel Security Policy to include completed background investigations (as required) prior to classified performance. This contract shall include a DoD Contract Security Classification Specification (DD-254) as an attachment.

Facility Security Officers (FSOs) are responsible for notifying the MCSC AC/S G-2 Personnel Security Office (PERSEC Office) via encrypted e-mail to MCSC_Security@usmc.mil or 703-432-3374/3952 if any contractor performing on this contract receives an unfavorable adjudication. The FSO must also notify the PERSEC Office, within 24 hours, of any adverse or derogatory information associated with the 13 Adjudicative Guidelines concerning any contractor performing on this contract, if they have been issued a CAC, a MCSC Building Badge and/or granted classified access. The FSO shall notify the Government (written notice) within 24 hours of any contractor personnel added or removed from the contract that have been issued a Common Access Card (CAC) and/or a MCSC Building badge/access.

COMMON ACCESS CARD

The COR will identify and only approve those contractor employees performing on this contract that require CACs in order to perform their job function. In accordance with Headquarters, United States Marine Corps issued guidance relative to Homeland Security Presidential Directive – 12 (HSPD-12), all personnel must meet eligibility criteria to be issued a CAC. In order to meet the eligibility criteria, contractor employees requiring a CAC must obtain and maintain a favorably adjudicated Personnel Security Investigation (PSI). Prior to authorizing a CAC, the employee’s Defense Information System for Security (DISS) record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been submitted and accepted (opened). The minimum acceptable investigation is a T-1 or a National Agency Check with Written Inquiries (NACI). If a contractor employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked. CACs are not issued for convenience.

Facility Security Officers (FSOs) are responsible for notifying the MCSC AC/S G-2 Personnel Security Office (PERSEC Office) at 703-432-3490/3952 if any contractor performing on this contract receives an unfavorable adjudication after being issued a CAC. The FSO must also immediately notify the PERSEC Office of any adverse/derogatory information associated with the 13 Adjudicative Guidelines concerning any contractor issued a CAC, regardless of whether a DISS Incident Report is submitted.

Each CAC is issued with a “ctr@usmc.mil” e-mail account that the individual contractor is responsible to keep active by logging in on a regular basis (at least twice a month), sending an e- mail and clearing any unneeded e-mails. Contractors issued a CAC are prohibited from “auto- forwarding” e-mail from their .mil e-mail account to their .com e-mail account. If the “ctr@usmc.mil” e-mail account is not kept active, G-6 will deactivate the account and the CAC will also lose its functionality. Contractor employees shall solely use their government furnished “ctr@usmc.mil” e-mail accounts for work supporting the USMC, conducted in fulfillment of this contract, and shall not use a contractor supplied or personal e-mail account to conduct official U.S. government business. The use of a contractor or personal e-mail account for contractor business or personal use is allowed, but only when using cellular or a commercial internet service provider.

If a contractor loses their eligibility for a CAC due to an adverse adjudicative decision, they have also lost their eligibility to perform on MCSC contracts.

image1.jpeg