DRAFT_Base_IDIQ_PWS_Platform_Mission_Equipment_Software_Branch.docx

Performance Work Statement (PWS)

U.S. ARMY COMMUNICATIONS ELECTRONICS COMMAND (CECOM)

SOFTWARE ENGINEERING CENTER (SEC)

INTELLIGENCE, ELECTRONIC WARFARE & SENSORS (IEW&S) DIRECTORATE

Sensors & Mission Equipment (S&ME) Division

Platform Mission Equipment Software Branch (PMESB)

05/15/2020 Version 1.6

Acquisition Sensitive see FAR 3.104

Performance Work Statement (PWS) Mission Equipment (ME) Software Engineering Support Vision Statement

To provide outstanding system/software engineering support with cost effectiveness to customers while ensuring reliability, maintainability, interoperability, and configuration integrity of the software components for mission equipment.

1 Scope The scope of this PWS is to provide support services to CECOM SEC/IEW&S/S&ME -Platform Mission Equipment Software Branch (PMESB) in the following:

· Provide support for Post Deployment and Post Production (PPSS/PDSS) activities for the PMESB systems, including but not limited to systems described in Appendix C System Description.

· Provide system/software engineering and integration support for aviation systems, tactical Air Traffic Control, Position/Navigation/Terrain systems, Force Protection, and Command and Control systems.

· Provide MIL-STD-1553 engineering, validation and testing, and system integration support.

1.1 Background

The Software Engineering Center (SEC), PMESBBranch, is responsible for providing primary system/software engineering support to aviation navigation, communications, ground support avionics, Command and Control, Force Protection, and tactical Air Traffic Control systems during their development and integration into weapon systems. In addition, we are the lead Army Tri-Service organization for MIL-STD-1553 engineering, validation and test, and system integration support.

Post Production/Post Deployment Software Support: SEC PMESB currently is responsible for the Post Production/Post Deployment Software Support (PPSS/PDSS) of 13 Avionics and force protection Systems. The software maintenance entails making changes to software, testing the changes and releasing the software to the field in a timely manner. SEC PMESB is also responsible for the configuration management of all associated software and documentation for each of these systems. PMESB provides outstanding PPSS/PDSS support to systems sponsored by the following organizations:

· PEO IEWS, PM Force Protection Systems (FPS)

· PEO IEWS, PdM Electro-Optical/Infrared (EO/IR)

· PEO IEWS, PdM Combat Terrain Information Systems (CTIS)

· PEO GCS, PM Heavy Brigade Combat Team (HBCT)

· CECOM Logistics and Readiness Center (LRC) Airborne Battle Command Program Support Office (ABCPS) SOSE&I/Direct Reporting

· PM Position, Navigation, and Timing (PNT) Navy Naval Air Systems Command (NAVAIR) PEO Aviation, PdM Assured Airspace Access Systems (A3S) PEO Aviation, Aviation Architecture Environment Exploitation (A2E2) PEO Solider, PM Air Warrior (AW)

· U.S Coast Guard U.S. Marines U.S. Air Force

· U.S. Air Force System/Software Engineering and Integration: The PMESB provides expert system/software engineering support for avionics systems throughout their life cycle. Following development, the PMESB plays an expert role during the integration of these avionics systems into weapon/aircraft systems such as the Improved Cargo Helicopter (ICH), HH-60L (MEDEVAC), RC-12 Guardrail Common Sensor, OH-58D, AH-64A/D and SOA aircraft (MH-47E and MH-60L). Support includes requirements definition, analysis, design, interface control working groups, technical interchange, test planning, and document generation/review to include the preparation or validation of MIL-STD-1553 Multiplex Interface Control Document (MICD) and Software/Interface Requirements documents. Expert support in the area of MIL-STD-1553 and Ethernet is invaluable considering that the above weapons systems are integrated around the MIL-STD-1553 and/or Ethernet network.

MIL-STD-1553: SEC PMESB offers engineering experience and expertise on all aspects of MIL-STD-1553 matters, ranging from participating in the writing of MIL-STD-1553 requirements to providing avionics maintenance test systems. The Validation and Test Facility (VALFAC) is a test laboratory that provides independent MIL-STD-1553 Validation and Verification test services for DoD MIL-STD-1553 subsystems in accordance with Tri-Service test standards. VALFAC will enable US Army and other DoD components to continue ensuring Contractor Furnished Equipment (CFE) and Government Furnished Equipment (GFE) meet the requirements of governing communications standards.

1.2 Contract Type

This contract is proposed to be a single award, five-year Indefinite Delivery Indefinite Quantity (IDIQ) contract with Cost Plus Fixed Fee (CPFF)- Completion and CPFF- Level of Effort (LOE) task orders, for all line items other than travel and materials. Travel and materials are on a Cost basis in accordance with FAR 16.302.

The Government anticipates CPFF Level of Effort (LOE) Task Orders to be established for PPSS/PDSS Support (Operations and Maintenance Army (OMA) funds), In Accordance With (IAW) PWS 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, .2.8, 3.2.9. This will be about 80% of the work.

The Government anticipates CPFF Completion Task Orders to be established for customer requirements, to include System/Software Engineering Support to PM/PEO (Research, Development Test & Evaluation (RDT&E)), IAW PWS: 3.2.4. 3.2.6, 3.2.7, 3.2.9; Software Engineering Environment Maintenance Effort (Procurement Funds), IAW PWS 3.2.5; and Foreigm Military Sales (FMS) Support, IAW PWS 3.2.4. The contractor will be required to meet all requirements in the PWS, at the level specified in the Acceptable Quality Levels (ACLs), and to compliant with all deliverables as specified in the CDRLs.

1.4 Period of Performance

The period of performance shall be delineated in each task order as requirements are known.

1.5 Place of Performance

1.5.1 Onsite (Government Facility)

Performance of the requirements set forth within this PWS shall be conducted at the Communications-Electronics Command-Life Cycle Management Command (CECOM-LCMC) SEC facility at Building 6006 Combat Drive, Aberdeen Proving Ground (APG), MD 21005. The contractor in support of this requirement shall utilize these facilities as the primary locations for management, system & software engineering, and software maintenance work. The Government will provide on-site Contractor personnel with adequate workspace and equipment/material (to include desks, chairs, cabinet space, and telephones), and access to printers, FAX machine, scanners and photocopiers at the Government facility where the work will be performed for contractor use on a rent-free basis IAW FAR 52.245-9.

1.5.2 Offsite (Contractor Facility)

In order to maximize productivity during performance of the contract with the optimal utilization of the Government laboratory, all contractor engineers are required to work on site. Other performance associated with contractor office administration are allowed to work off-site, as specified in Appendix A – Level of Effort 2 Applicable Documents and Websites The following documents and websites are referenced for the performance of this contract. The Government reserves the right to update applicable documents.

Reference Websites:

http://www.dtic.mil/dtic/ http://www.apd.army.mil/

Governing Documents:

Joint Travel Regulations (JTR) https://www.defensetravel.dod.mil/Docs/perdiem/JTR.pdf

AR 715-9, Operational Contract Support Planning and Management http://www.apd.army.mil/pdffiles/r715_9.pdf

AR 25-1, Army Information Technology www.apd.army.mil/pdffiles/r25_1.pdf

AR 25-2, Information Assurance http://www.apd.army.mil/pdffiles/r25_2.pdf

AR 735-5, Property Accountability Policies http://www.apd.army.mil/pdffiles/r735_5.pdf

DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology http://www.dtic.mil/whs/directives/corres/pdf/851001_2014.pdf

CNSSI No 1253, Security Categorization and Control Selection for National Security Systems https://www.cnss.gov/CNSS/issuances/Instructions.cfm (search for No 1253)

NIST 800-53 Rev 4, Security and Privacy Controls for Federal Information Systems and Organizations http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf

05-PR-M-0002, Army Best Business Practice for Information Assurance Training https://atc.us.army.mil/iastar/docs/Training_BBP.pdf

DoD 8570.01-M, Information Assurance Workforce Improvement Program http://www.dtic.mil/whs/directives/corres/pdf/857001m.pdf

AR-380-67, Personnel Security Program www.apd.army.mil/pdffiles/r380_67.pdf

Reference Documents:

CECOM Policy Memo No. 13-11 Information Technology (IT) Strategic Planning, Acquisition, and Accreditation Procedures PWS Attachment 1

SEC SOP E-09 22 April 2012 PWS Attachment 2

IEWS-CM-202, IEWSD Configuration Management Process Description (CM PD) Document PWS Attachment 3

CECOM Pamphlet 25-1 U.S. Army Communications- Electronics Command (CECOM) Standard Operating Procedures (SOP) for Information Technology (IT) Acquisitions PWS Attachment 4

SEC Lab Configuration Control Board (CCB) Configuration Baseline v1.0 August 2012 (To be provided upon award)

AR 73-1 Test and Evaluation Policy https://acc.dau.mil/adl/en-US/649679/file/71925/r73_1%5B1%5D.pdf

AS4111 Validation Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Remote Terminals 1998-10-01 http://standards.sae.org/as4111

AS4112 Production Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Remote Terminals 1989-01-11 http://standards.sae.org/as4112

AS4113 Validation Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Controllers 1989-01-11 http://standards.sae.org/as4113

AS4114 Production Test Plan for the Time Division Command/Response Multiplex Data Bus Controllers 1989-01-11 http://standards.sae.org/as4114

AS4115 Test Plan for the Digital Time Division Command/Response Multiplex Data Bus System 1989-01-11 http://standards.sae.org/as4115

AS4116 Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Monitors 1990-09-10 http://standards.sae.org/as4116

AS4117 Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Couplers, Terminators, and Data Bus Cables 1991-03-19 http://standards.sae.org/as4117

Department of the Army Pamphlet 738-751 Functional User’s Manual for the Army Maintenance Management System-Aviation http://www.apd.army.mil/pdffiles/p738_751.pdf

3 Requirements

3.1 General

3.1.1 Materials, Equipment and Facilities

3.1.1.1 Government Furnished

Government Furnished Material (GFM) and Government Furnished Equipment (GFE) may be provided to support individual Task Orders. In such cases, the GFM and GFE clauses will be included in the corresponding Task Order. The Contractor shall be responsible for conducting all necessary examinations, inspections, maintenance and tests. The Contractor shall be responsible for reporting all inspection results, maintenance actions, losses and damage to the Government. If the Contractor loses or damages the equipment, it will be the Contractors responsibility to replace or repair the equipment to the Government’s satisfaction at no additional cost to the Government. GFM/GFE items, except consumables, shall be returned to the Government in good condition upon termination of the Task Order. The determination of "same condition” will be made by the Contracting Officer’s Representative (COR) or designee. A list of government furnished materials, equipment, and facilities for this contract is provided in Appendix K..

3.1.1.2 Contractor- Acquired/Lease

The Contractor may be required to purchase the hardware and/or software necessary to accomplish the efforts specified within this PWS. Purchases must be made through Computer Hardware, Enterprise Software and Solutions (CHESS). Any purchased software and/or hardware shall become the property of the Government and used by the Contractor for the completion of the specific task. Software integrity shall be maintained by the Contractor within the licensing agreement of the producer until such software is delivered to the Government, or otherwise disposed of in accordance with Government direction. The Contractor shall provide three cost estimates to the Procuring Contracting Officer (PCO) or designee for review and/or approval prior to purchase, as required by the PCO or designee. The Contractor shall not purchase any third party software license or maintenance agreements under this contract without the expressed written consent from the Contracting Officer in advance of the purchase.

3.1.1.3 Accountability

Any loss or damage to GFM/GFE/Contractor Acquired Property (CAP) shall be reported to the PCO or designee, identified within the contract, within three (3) days of the discovery. A statement explaining the circumstances of the loss/damage shall be submitted on a DA Form 4697, Report of Survey. The Contractor shall provide a quarterly status report of GFM/GFE IAW the CDRL, Data Item Description DI-MGMT-80269 Status of GFE Report.

3.1.2 Security

The highest level of facility clearance required for the contractor to perform on this contract is SECRET. All positions/labor category equivalents require a SECRET security clearance at time of award. The highest level of classified material the contractor will be required to safeguard at its own facility is NONE.

The following security requirements apply to this contract and are further described in the DD Form 254, Contract Security Classification Specification (See Appendix G):

· This contract will require access to Communications Security (COMSEC) information.

· This contract will require access to For Official Use Only Information (FOUO).

· In performing this contract, the contractor will have access to classified information only at a government activity.

· In performing this contract, the contractor will have operational security (OPSEC) requirements.

3.1.3 Inspection and Acceptance / FOB

Inspection and acceptance shall be at destination.

Ship to address is:

Attention: Denise McKillop, COR US Army CECOM LCMC SEC PMESB SEC 6006 Combat Drive, Aberdeen Proving Ground, MD 20015.

DODAAC: W90W2B

All deliverables shall be delivered to the Government IAW PWS paragraph 3.2 and Appendix D.

3.1.4 Phase In and Phase Out

A transition period is scheduled for a sixty (60) day period immediately following the contract start date (phase in) and a sixty (60) day period prior to contract end date (phase out) to allow for orderly contract transition. In order to maximize the effectiveness of the transition process, an initial meeting between the Government's Contracting Officer’s Representative and Contract Managers for the incoming and outgoing Contractors shall be held to address phase in and phase out requirements and responsibilities no later than seven (7) days into the phase in/phase out period, and subsequent meetings will be held as determined by the PCO, but not less than weekly thereafter.

When an incumbent contractor is also the successor contractor, these meetings will not be waived, since the orderly transition from one work specification to another will also require significant management involvement in the transition process.

3.1.4.1 Phase In

During the phase in period, contractor personnel will be permitted to observe operation of the contractor and Government pertaining to this contract. The incoming contractor shall ensure that its phase in operations do not hinder or interfere with normal operations of the phase out contractor and do not result in loss of productivity. During the phase in, the outgoing contractor will transfer all work at contract start date to the successor contractor.

3.1.4.2 Phase Out

During the period immediately prior to the end of this contract, if the contractor is not awarded the subsequent contract for these services, the contractor shall permit his successor to observe and become familiar with any and all operations under this contract. The contractor shall remain responsible and liable for the completion of all requirements of this contract, which shall begin on or before the final day of this contract. The contractor shall not defer any requirements for the purpose of avoiding responsibility and transferring such responsibility to the successor, contractor or the Government. The contractor shall fully cooperate with the successor contractor and the Government, and shall not interfere with their work or duties.

3.1.4.2.1 Phase Out Plan

The contractor shall provide the Contracting Officer with a phase out plan no later than 90 days prior to the contract end date, IAW the CDRL, Phase Out Plan DI-MISC-80508B. This plan shall detail disposition action for all furnishings, equipment, and documentation with moderate Government input, outlining the Contractor’s approach to fulfill the requirements of this Contract and applying all relevant factors and information gathered throughout the performance of the contract.

3.1.5 Post Award Orientation Meeting

A post award orientation meeting shall be held at the government's facility at APG, Maryland within thirty (30) working days after award of contract. This provision shall in no way constitute grounds for excusable delay by the contractor in performance under any provisions of the contract.

3.1.6 Travel

The contractor shall be required to travel to other Government installations or to contractor facilities within CONUS to observe or conduct tests, ensure compatibility of configuration changes and other integration services, investigate and resolve network issues, and to furnish technical guidance and operational support as required. Trips and numbers and types of personnel will be limited to the minimum required to accomplish work requirements. The contractor will be responsible for arranging all contractor personnel travel at the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles, and in accordance with the applicable C4ISR and local command policies as well at the Joint Travel Regulations (JTR) and AR 715-9.

There will be no reimbursement for local travel within 50 miles in and around the place of performance.

A summary of anticipated travel is provided in Appendix E.

3.1.6.1 Travel Arrangements

Air travel will be accomplished on regularly scheduled commercial flights in the most economical manner consistent with the successful accomplishment of the mission. Reimbursement for the cost of lodging and incidental expenses will be considered to be reasonable and allowable to the extent that costs submitted for reimbursement do not exceed the rates and amounts allowed by the JTR (https://www.defensetravel.dod.mil/site/perdiem.cfm), as applies to civilian employees of the United States Government.

All CONUS travel shall be in accordance with the contractual requirements set forth within this PWS. All CONUS and extended CONUS travel details must be provided to the COR and approved by the Contracting Officer prior to the commencement of travel. The contractor shall perform duties such as Temporary duty (TDY). Locations may include CONUS sites listed in Appendix E of this PWS.

Trips and numbers and types of personnel will be limited to the minimum required to accomplish work requirements. The contractor shall be responsible for arranging all contractor personnel travel at the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles. All CONUS travel will be on a cost-reimbursement basis.

3.1.7 Personnel Qualifications

The contractor shall employ only personnel who meet the minimum qualifications provided under Appendix A and the subsections below, and are fully qualified and competent to perform the tasks specified in this PWS. The contractor shall ensure that such personnel are utilized in a manner that maximizes productivity and efficiency. For purposes of surveillance, resumes of contractor personnel performing support services as described within this PWS are subject to verification by the COR to ensure that the support personnel meet or exceed the proposed category descriptions, qualifications, and possess the minimum technical skills and experience specified at Appendix A of this PWS.

Four of the labor categories included in Appendix A are considered to be critical and essential to work performance. The critical labor categories include the following: Engineering Supervisor – Senior/Lead, Software Developer – Senior/Lead, System Administrator – Journeyman, and the System Engineer – Senior/Lead. At least 30 days prior to diverting any of the specified individuals to other programs or contracts (or as soon as possible, if an individual must be replaced, for example, as a result of leaving the employ of the Contractor), the Contractor shall notify the Contracting Officer and shall submit, IAW CDRL E001 DI-MGMT-80269 Status Report/Critical Personnel Change, comprehensive justification for the diversion or replacement request (including proposed substitutions for critical positions) to permit evaluation by the Government of the impact on performance under this contract. The Contractor shall not divert or otherwise replace any critical personnel without the written consent of the Contracting Officer. The Government may modify the contract to add or delete key personnel at the request of the contractor or Government. Critical positions shall be filled within thirty (30) calendars days of any vacancy. Non-critical positions shall be filled within forty-five (45) calendar days of any vacancy.

3.1.7.1 Domain Knowledge

The contractor shall provide qualified personnel who demonstrate via the successful performance of the tasks within this PWS, subject matter expertise, engineering knowledge of, and experience with aviation and avionics systems associated with data bus network/interface (MIL-STD-1553, ARINC 429, RS-232, RS-422, RS-423, and Ethernet), Air Traffic Control, Command and Control (C2), and aircraft/LRU maintenance.

3.1.7.2 Technical Skills

The contractor shall provide qualified personnel who demonstrate via the successful performance of the tasks within this PWS, engineering and development capabilities with

· C# in .NET Runtime Environments

· Visual Basic 6

· C++

· Microsoft Access

· Software Product Line Methodology & Development

· Microsoft Server

· Microsoft Visio Additionally, contractor personnel shall be proficient in the utilization of electronic and software tools including Microsoft Office, Project, and SharePoint.

3.1.8 Work Hours

The contractor is responsible for conducting business, between the hours of 0800 and 1700 Monday thru Friday except Federal holidays. When the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings; contractor personnel who normally work in the closed Government facility are not responsible for conducting business. The Contractor shall not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is open for operations.

3.1.9 Contractor Manpower Reporting (CMR)

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor shall report ALL contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor is required to completely fill in all the information in the format using the following web address https://cmra.army.mil/ The required information includes:

1. Contracting Office, Contracting Officer, Administrative Contracting Officer;

2. Contract Number;

3. Beginning and ending dates covered by reporting period;

4. Contractor name, address, phone number, email address, identity of contractor employee entering data;

5. Estimated direct labor hours (including sub-contractors);

6. Estimated direct labor dollars (including sub-contractors);

7. Total payments (including sub-contractors);

8. Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor, if different);

9. Estimated data collections cost;

10. Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information);

11. Locations where contractor and subcontractor perform the work (specified by zip code in the United States or nearest city, country when in an overseas location, using standardized nomenclature provided on website);

12. Presence of deployment or contingency contract language; and

13. Number of contractor and sub-contractor employees deployed in theater during this reporting period (by country).

As part of its submission, the contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending September 30 of each calendar year. Contractors may use a direct XML data transfer to the data base server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor's systems to the secure web site without the need for separate data entries for each required data element at the web site. The specific formats for the XML direct transfer may be downloaded from the web site. The Contractor shall NOT mark any data provided to the USG under this contract as proprietary; this includes records, files, memoranda, reports, listings, SOPs, plans, programs, studies, tests, property listings, etc., or any other data acquired or produced by the Contractor in support of this contract.

3.1.10 Contractor Mandatory Training

In discharging its responsibility under the contract, the contractor shall only use fully trained, experienced, appropriately certified, and technically proficient personnel. Consistent with the Defense Federal Acquisition Regulation Supplement (DFARS) 252.239-7001, Information Assurance Contractor Training and Certification, the contractor shall ensure that personnel accessing information systems have the proper and current IA certification required to perform IA functions IAW DoD 8570.01-M, Information Assurance Workforce Improvement Program.

The Contractor shall meet the applicable IA certification requirements, including: DoD-approved IA workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; and appropriate operating system certification for IA technical positions as required by DoD 8570.01-M.

Upon request by the Government, the Contractor shall provide documentation supporting the IA certification status of personnel performing IA functions. Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing IA functions. The Army’s implementation of the above requirements for IA Training, Certification, and Workforce Management, are found in AR 25-2, Information Assurance, and the associated Army Best Business Practice for Information Assurance Training, 05-PR-M-0002.

The contractor shall complete all government mandated training requirements as determined by CECOM SEC PMESB Branch for contractor employees that occur during the period of performance for this contract. Contractors shall track Mandatory Training compliance using their own resources and provide a report of status to the Government. Evidence of compliance shall be presented upon Government request.

3.1.11 Employment of Foreign Nationals

All contractor personnel, including subcontractors and consultants, must satisfy certain personnel security standards whether or not the information processed by the Automated Information System (AIS) on which they are working is classified. Contractors working with unclassified AIS documents will have their positions designated Automatic Data Processing (ADP) I, II or III by the Government. Foreign nationals should generally not be allowed to perform work on contracts that would allow them access to unclassified sensitive information, and they will not be employed in positions that meet the definition of ADP I or II unless specifically approved by HQ AMC. Definitions of ADP I, II and III are located in AR 380-67, Personnel Security Program, paragraph 3-614.

3.2 Performance

Specific performance requirements will be specified in the PWS for each task order.

The Quality Assurance Surveillance Plan (QASP) at Appendix B will be used to assess the contractor’s performance to ensure compliance with the Government’s performance objectives.

4 Deliverables Data shall be delivered IAW the attached CDRLs, DD Forms 1423, which cite the Data Item Descriptions (DIDs) or other appropriate references for technical data and other information required during the performance of this contract.

5 Data Rights The Government's rights in non-commercial technical data and software deliverables shall be governed by DFARS 252.227-7013 and DFARS 252.227-7014, respectively. Pursuant to the requirements set forth in DFARS 252.227-7017, Offerors are required to specifically identify Data/Software Rights Assertions related to technical data and software deliverables. As indicated in DFARS 252.227-7017(e), an Offeror's failure to submit, complete, or sign the aforementioned Data and Software Rights Assertions with its offer may render the offer ineligible for award. Additional provisions related to technical data and software rights are provided in Appendix (F).