DRAFT_-_ICMSD_PWS.pdf

FA9304-18-F-0001

ATTACHMENT 1

PERFORMANCE WORK STATEMENT (PWS)

FOR

INSTRUMENTATION CONFIGURATION, MANAGEMENT,

SUPPORT AND DEVELOPMENT II

(ICMSD II)

412th Test Engineering Group

EDWARDS AFB, CA

1 AUGUST 2018

TABLE OF CONTENTS

SECTION PAGE

1.0 BACKGROUND 3

2.0 SCOPE OF WORK 3

3.0 PRODUCTS 3

3.1 Hardware

3.2 Software

4.0 SERVICES 4

4.1 Maintenance Services

4.2 System Enhancements and Development

4.3 Training

4.4 Knowledge Management / Data Analysis / Data Mining

4.5 Installation and Initial Start-up

4.6 Transitions and Turnovers

4.7 Travel

5.0 DELIVERABLE DATA 10

5.1 Status Reports

5.2 Capabilities Matrix

5.3 Manuals and Licenses

5.4 Engineering Documentation

5.5 Documentation Maintenance and Archive

5.6 Software and Database Repository

6.0 CONTRACT DATA REQUIREMENTS LIST 14

7.0 ORDERING PROCEDURES 15

8.0 ORDER PRICING 15

9.0 SERVICE DELIVERY SUMMARY 16

10.0 GOVERNMENT FURNISHED SUPPORT 17

10.1 Government Furnished Property

10.2 Government Facilities/Support

10.3 Contractor Individual Access

10.4 Contractor Access Cards

11.0 Contractor Manpower Reporting 17

12.0 General Information 17

12.1 Contract Quality Assurance.

12.2 Controlled Unclassified Information, Covered Defense Information

12.3 Contractor Points of Contact

12.4 Base Access

12.5 Security Requirements When Visiting DoD Facilities

12.6 Environmental Protection

1.0 Background.

Provision for all aspects of flight test instrumentation implementation are required in order to support data acquisition systems used in the overall flight test effort. This Performance Work Statement (PWS) describes the contract work required to support the data acquisition systems.

The Instrumentation Loading, Integration, Analysis and Documentation (ILIAD) design allows different organizations to contribute and share information relevant to the design, maintenance and support of real-time instrumentation systems. ILIAD is designed to provide the tools necessary to manage information, program instrumentation and analyze test data. The primary goal is to support test engineers and technicians with automated tools for programming support, pre-flight validation, and post-test analysis for airborne and ground-based systems. The system has been designed to enable engineers to batch process jobs for the conversion of digitized raw data into user specified raw samples or engineering units that can be output into several format types. The system supports an enterprise level web-based data mining application which allows multiple engineers to concurrently search, retrieve and analyze large amounts of test data – quickly and readily. These systems operate on Commercial Off-The-Shelf (COTS) computer hardware, data storage systems, associated peripherals and components assembled, configured and integrated to meet instrumentation configuration requirements.

2.0 Scope of Work.

The contractor shall provide all personnel, equipment, tools, materials, vehicles, supervision, other items and services necessary, except as specified in Section 7.0, Government Furnished Property (GFP), to perform Instrumentation Configuration, Management, Support and Development (ICMSD) related to ILIAD and flight test instrumentation systems operation. This support includes maintenance and operational services; engineering technical services and development; materials and equipment; system enhancement and software/hardware modifications; integration; emergency repairs; manuals, documentation and licenses to include legacy systems.

The contractor shall provide COTS products and services as listed in the contract price list at Exhibit B, unless otherwise specified, and as outlined in the Delivery and/or Task Order, (hereby referred to as “order”), as authorized by the Contracting Officer (CO).

The contractor shall coordinate activities to achieve order objectives through the designated Government Project Manager (PM), unless otherwise specified in orders.

3.0 Products. Product pricing and delivery terms will be as listed on Exhibit B, unless otherwise specified in orders. Inclusion of Non-Developmental Items, GFP, or products not listed on Exhibit B and in price quotations, proposed systems, or product deliveries shall only be at the direction of the Government through a Request for Proposal (RFP) and subsequent order signed by the CO. (CDRL 002)

3.1 Hardware.

The contractor shall provide automated data processing equipment (ADPE), computer data center equipment, data network equipment, and data center supplies as listed on Exhibit B and as specified in orders.

Hardware provided shall be the vendor’s COTS component products. Products may be assembled or integrated into higher level more complex systems.

The contractor may propose new, upgraded or modified lines of equipment for addition to Exhibit B, provided the equipment is production ready and not in a developmental state. For new, upgraded, or modified lines of equipment proposed to replace older, obsolete, or discontinued equipment, the contractor shall describe the relationship between the equipment. In order to be added, the contractor shall describe the unique nature of the proposed addition, above and beyond other commercially available similar equipment. Warranties shall remain in effect on discontinued equipment and shall be kept (and identified) on Exhibit B.

3.2 Software.

The contractor shall provide ADPE software, as listed on Exhibit B and as specified in orders. Software provided shall be the vendor’s COTS products.

The contractor may propose new, upgraded, or modified lines of software for addition to Exhibit B, provided the software is production ready and not in a developmental state. For new, upgraded, or modified lines of software proposed to replace older, obsolete or discontinued software, the contractor shall describe the relationship between the software. In order to be added, the contractor shall describe the unique nature of the proposed addition, above and beyond other commercially available similar software. Warranties shall remain in effect on discontinued software and shall be kept (and identified) on Exhibit B.

4.0 Services.

Services pricing and delivery terms will be as listed on Exhibit B unless otherwise specified in orders.

The contractor shall apply professional project management knowledge, skills, tools and techniques to project activities to meet project requirements. The contractor shall describe the project management method and metrics used to manage tasks.

The contractor shall perform risk assessments and apply best practice risk management techniques during all stages of task execution. All concerns considered to be High Risk before mitigation action shall be specifically reported to the Government Order Point of Contact as soon as practical, and no more than 30 days after discovery.

Services in support of flight test data acquisition, processing, analysis, storage, and in support of the ILIAD software suite (and supported equipment database) including technical support (e.g. answering questions about usage, configuration, suitability, and correct performance of software), software engineering and development, database engineering and development, change control, configuration control, and configuration management of the ILIAD Toolset shall be provided as specified in orders.

Services also include:

On-site and remote engineering support, maintenance and repair support for databases, software, and hardware referenced in this document;

Requirements elicitation, documentation, and analysis;

Database, software, and hardware design; database, software and hardware engineering;

Database and software development, hardware fabrication;

Component and system testing for hardware, software, and databases;

Component and system integration for hardware, software, and databases;

Component and system installation and start up;

Hardware, software, and database change management;

Database, software, and hardware configuration management, and other services to develop and maintain flight test data applications and systems; and Training.

The contractor may propose new, upgraded, or modified services for addition to Exhibit B. For new, upgraded, or modified services proposed to replace older, obsolete or discontinued services, the contractor shall describe the relationship between the services. In order to be added, the contractor shall describe the unique nature of the proposed addition, above and beyond other commercially available similar services. Maintenance support shall remain in effect on discontinued hardware and software and shall be kept on Exhibit B.

4.1 Maintenance Services

Maintenance Services shall include diagnostics, recommended maintenance actions, actual maintenance actions, recommended repairs, actual repairs, and verification and validation of the repaired system.

Maintenance services may be ordered on a per task basis depending on individual program requirements. The particular type of maintenance service will be specified in orders.

The contractor shall provide a Teardown Deficiency / Recommended Repairs Report and a Repair Status Report as needed for each order. (CDRL 011, 010)

The contractor shall utilize spares and/or replacement parts previously purchased by the Government for these services when available. For parts not on hand, price proposals shall be prepared and presented to the CO for further action and approval.

The contractor shall minimize operating flaws (i.e. bugs), and shall enhance compliance with security classification, cybersecurity, information assurance, government accreditation requirements, and industry best practices.

4.1.1 System Sustainment Services.

The contractor shall provide services required to prevent failure, to prevent cybersecurity vulnerability, and to maintain correct operation and performance of hardware, software, and/or database systems as specified in orders.

The contractor shall provide services, including labor and parts, to perform diagnostics and perform maintenance actions as needed on designated equipment as specified in orders.

The contractor shall provide services to perform diagnostics and maintain database and software items for compatibility with their target operating systems, system hardware architecture and Government operational environment requirements, (i.e. bug fixes and compatibility patches).

Patches or new releases shall be issued as required to mitigate known cybersecurity issues, hazards and defects. Verification and validation of proposed new databases or software, or changes to existing databases or software shall be performed before release. The contractor shall provide regular progress reports for work in progress but not yet released. (CDRL 012)

4.1.2 Telephone Diagnostic Assistance. The contractor shall make available remote assistance, as identified in orders, utilizing voice and online connections (e.g. telephone, mobile phone, text messaging).

4.1.3 Repair Maintenance (On-Call, On-Site).

The contractor shall provide repair maintenance services required to resolve cybersecurity issues and to restore correct operation and performance of designated hardware, software, and/or database systems.

The contractor shall provide services on a routine or an emergency basis, including labor and parts, to perform diagnostics and repair as needed of designated equipment as specified in orders.

The contractor shall provide services on a routine or an emergency basis to perform diagnostics and repair (configuration or code modification) as needed of designated supported databases or software as specified in orders.

Patches or new releases shall be issued as required to mitigate known cybersecurity issues, hazards, and defects. Verification and validation of proposed new databases or software, or changes to existing databases or software, shall be performed before release. The contractor shall provide regular progress reports for work in progress but not yet released.

The government has the option to specify that a repair shall use only GFP test equipment/computers at Government locations.

4.1.3.1 Routine Repair. Upon notification that equipment is malfunctioning or inoperative, contractor personnel shall arrive at the Government’s installation site within twelve (12) working hours, if located within fifty (50) miles of a service center. Beyond fifty (50) miles, dispatch contractor personnel not later than twenty-four (24) hours after notification. Excluded from these periods are Saturdays, Sundays, and Federal holidays unless it has been otherwise specified in the order.

4.1.3.2 Emergency Repair. Emergency Repair Service will be available up to seven days a week, 24 hours a day as requested in orders. Obligation may be provided on the order in advance, or on an as-needed basis.

4.1.3.2.1 Equipment Emergency Repair. Contractor personnel shall arrive at the Government’s installation site within 12 hours of notification that equipment is malfunctioning or inoperative, unless otherwise specified in the order.

4.1.3.2.2 Software Emergency Repair. Contractor personnel shall initiate repair response within 12 hours of notification that databases or software are malfunctioning or inoperative, unless otherwise specified in the order.

4.1.4 Software Service Programs.

The contractor shall provide database and software trouble reporting services as specified in orders.

The contractor shall receive and record software trouble reports and software enhancement requests for any database or software covered in any maintenance task or warranty agreement. The contractor shall sequentially label trouble reports and enhancement requests received. The contractor shall investigate the root cause of reported trouble and shall propose solutions to resolve the trouble. The contractor shall estimate and propose solutions for requested enhancements.

The contractor shall report status of all trouble reports, enhancement requests, and sustainment, repair, or warranty work, including all work completed, in-progress, scheduled to start, and not scheduled.

(CDRL 003, 012)

4.1.5 Repair and Replacement.

The contractor shall provide exchange, repair, refurbishment or installation services at the Contractor’s facility or other designated locations for Government owned hardware products as specified in orders.

All parts furnished will be new standard parts or parts of equal quality, and shall be identified as such.

For equipment repairs, the contractor shall provide all labor, parts and modifications deemed necessary.

(CDRL 002, 010, 011)

Any parts of equipment with potentially classified information (e.g. memory modules, disc media, tape media, etc.) will remain in custody of the Government.

4.2 System Enhancements and Development.

The particular type of system enhancements or development (performance and functionality) will be specified in task requirements and as defined in the Government provided Technical Requirements

Document, PWS and order. The contractor shall provide services using the labor categories as listed on Exhibit B. (CDRL 002)

The contractor shall demonstrate their Software Development Life Cycle (SDLC) is in accordance with ISO/IEC TR 29110 “Systems and Software Engineering – Lifecycle profiles for Very Small Entities (VSEs)”, or other recognized commercial best practice for SDLC. (CDRL 021)

For database/software enhancement or development tasks, the contractor shall identify the development method to be used. Changes to the development methodology shall be as mutually agreed with the PM and CO. The contractor shall provide regular updates describing progress achieved for each enhancement or development task on contract. The contractor may be required to provide updates describing progress achieved for individual tasks.

Services include providing technical support for, fabrication of, or delivery of one-of-a-kind special support hardware built to the user's specifications, as required.

Contractor services shall include system requirements reviews (SRR), preliminary design reviews (PDR), critical design reviews (CDR), technical interchange meetings, meeting minutes, technical reports, prototyping and fabrication, component and system testing, verification and validation testing, and other technical reviews and technical activities as needed, consistent with system engineering best practices and task requirements. (CDRL 020, 021)

The contractor shall provide hardware, software, database integration engineering, design, build and testing in order to minimize operating flaws (e.g. software bugs, safety hazards), and to enhance compliance with security classification, cybersecurity, information assurance, government accreditation requirements, operational safety, and industry best practices.

Updated Manuals or Test Procedures and Reports shall be delivered as appropriate if required by the effort (e.g. CDRL 004, 005, 006 as applicable).

4.2.1 Software Enhancements and Development.

The contractor shall provide services to implement proposed database and software enhancements or developments. The particular type of database and software enhancements and system modification will be specified in orders. (CDRL 049, 037, 035)

An enhancement is defined as a modification beyond a configuration change that adds or alters functionality to a software or database item, or substantially increases its reliability, maintainability and useful life beyond ordinary sustainment or repair. The modification shall be at the request of the Government to meet a specific requirement. Enhancements shall also include modification for compatibility with new target operating systems, system hardware architectures or Government operational environment requirements. An existing software that is on Exhibit B that adds capability to a system without modification is not considered an enhancement.

A development is defined as a new software item or database item creation with a given functionality.

The development shall be at the request of the Government to meet a specific requirement.

Software created, enhanced or developed under the contract shall include Unlimited Government Purpose rights to original or source code, and to all additional files and procedures necessary to create running software.

Databases created, enhanced or developed under the contract shall include Unlimited Government Purpose rights to the database schema, structure, all queries and views, and to all additional scripts or code used to manipulate the database.

4.2.2 Hardware Enhancements and Development.

The contractor shall provide services to implement proposed hardware enhancements or development.

The particular type of hardware enhancements and system modification will be specified in orders.

An enhancement is defined as a modification that adds or alters the form, fit, function of an item, or substantially increases its reliability, maintainability and useful life beyond ordinary sustainment or repair.

The modification shall be at the request of the Government to meet a specific requirement.

Enhancements shall also include modification for compatibility with new target operational environment requirements. An existing piece of equipment that is on Exhibit B that adds capability to a system without modification is not considered an enhancement.

A development is defined as a new hardware item creation with a given functionality. The development shall be at the request of the Government to meet a specific requirement.

Hardware enhanced or developed under the contract shall include Unlimited Government Purpose rights to system design, architecture, implementation details, and specifications.

Enhancements to existing legacy equipment will be reviewed independently by the Government to determine best value at the Government’s discretion.

4.2.3 Studies, Analysis of Alternatives and Technical Requirements Document.

The contractor shall perform Systems Engineering studies related to contemplated System Enhancements and Development. The type of study will be specified in orders. (CDRL 021)

The contractor shall provide Analysis of Alternatives (AoA) services to assess critical technology elements (CTEs) associated with each proposed materiel solution and system requirement identified in the order, including; technology maturity, integration risk, manufacturing feasibility, and, where necessary, technology maturation and demonstration needs. The contractor shall propose no less than three alternatives suitable to satisfy the requirement identified in the order. The contractor shall propose alternatives that maximize use of non-proprietary (or “free/open”), non-developmental, and commercially available components and processes to be integrated. Inclusion of proprietary, developmental, or non-commercial components or processes, if necessary, shall be justified in the documentation.

The contractor shall propose Measure of Performance and Key Performance Parameter metrics, including thresholds and goals, for each AoA alternative. The contractor shall compare the operational effectiveness, operational suitability, life cycle costs, and developmental risks of alternatives proposed to satisfy the Government requirement.

The contractor shall analyze high level system requirements, and through disciplined Systems Engineering processes, shall decompose them into lower level implementation technical requirements and alternatives.

The contractor shall provide an AoA report, and one or more Technical Requirements Documents (TRDs) to document the results of the analysis.

4.3 Training.

The contractor shall provide technical training for products provided under the contract.

For products listed on Exhibit B, the contractor shall define the delivery method and quantity of training support (e.g. at the factory, via telecommunications, via field support, etc.), that will be provided as normal COTS product support.

For products developed as System Enhancements / Development, the contractor shall define the delivery method and quantity of training support (e.g. at the factory, via telecommunications, via field support, etc.), required to successfully field, operate and sustain the product.

The contractor may provide additional in-plant or on-site technical training support, as required, for their products under this contract that exceeds normal COTS product support.

Training may be ordered on an hourly basis or as a fixed block of time depending on individual program requirements for all products, to include but not limited to ILIAD, ODYSSEY, QLS, ETDMS and newly developed products. Training may include on-site services to provide assistance to Government technicians in diagnostic training. The type of training service will be specified in orders.

The contractor shall provide the proposed content of the training to the PM prior to beginning. No training shall begin until CO approval is obtained. (CDRL 002, 007)

4.3.1 Operational Training. The contractor may support training new operators to use Knowledge Management systems while generating operational results, up to a maximum of 40 hours per order.

4.4 Knowledge Management / Data Analysis / Data Mining.

The contractor shall provide data management, data storage, data analysis, data structure, and data display software, tools, equipment, systems, and procedures to examine flight test data sets and to report findings and results, consistent with requirements identified in task requirements.

Services, products, and procedures provided shall comply with security classification, cybersecurity, information assurance, government accreditation requirements, and industry best practices.

Any KM system must also meet system-wide requirements such as manageability, reliability, availability, maintainability, redundancy, scalability, usability, etc., while providing easy-to-use setup and configuration tools such that the KM system itself can be managed efficiently and without excessive cost.

The configuration of the KM data analysis data mining debrief quick look visualization reporting system is covered by Government purpose rights. (CDRL 002, 004, 005, 006, 037, 049)

4.4.1 Knowledge Management.

The contractor shall provide systems to create and maintain databases of flight test data and metadata as provided by the Government customer as specified in orders. The databases shall be used, transmitted, and stored consistent with the classification of their contents and sources.

Database data retrieval performance shall be consistent with customer requirements for execution time and throughput rate. Data retrieval and delivery to the customer shall be timely, as specified in the order.

4.4.2 Data Analysis. The Contractor shall provide systems to examine flight test data sets and in conjunction with defined algorithms shall analyze the data according to Government customer requirements as specified in orders.

4.4.3 Data Mining.

The Contractor shall provide systems to examine flight test databases to discover patterns, correlations, anomaly detection, dependencies, and trends within the data sets and to make predictions of flight test system performance as specified in orders.

The Contractor shall make use of algorithms as identified by Government customer and shall recommend other algorithms as necessary to segment the data and to evaluate the probability of future performance and events. Data retrieval and delivery to customer shall be timely, as specified in orders.

4.4.4 Debrief. The Contractor shall provide systems to examine flight test data sets of a single mission (of one or more sorties) and in conjunction with defined algorithms, extract and present those data and results in order to support post-flight mission debrief, with turnaround time as specified in orders.

4.4.5 Quick-Look. The Contractor shall provide systems to examine flight test data sets of a single mission (of one or more sorties) and in conjunction with defined algorithms, extract and present those data and results in order to support mission planning decision making for next day mission or other basis as specified in orders.

4.4.6 Visualization and Reporting. The Contractor shall provide systems to intelligibly visualize and automatically report flight test data sets as well as data analysis products to the appropriate test data customer as specified in orders.

4.4.7 KM performance and metrics. Any KM system provided shall have stated system performance goals and shall report actual system performance as specified in orders.

4.5 Installation and Initial Start-up.

The Contractor shall provide installation and initial start-up services for systems as required and as specified in orders.

The Contractor shall provide initial supplies, and operation and maintenance instructions for systems as required and as specified in orders.

All hardware components and assemblies shall be delivered in a cybersecure manner, either fully inspectable or with tamper evident seals in place on data handling equipment. Equipment inspection or PCA shall be performed before installation of data handling equipment.

All software executables, patches, firmware, source code, database scripts, schemas, and configuration data shall be delivered in a cybersecure manner, with checksums/hashes delivered via an independent channel.

4.6 Transitions and Turnovers.

For each activity or development, the Contractor shall provide a detailed plan describing a structured transition of responsibility to another provider. The transition plan shall include any necessary labor, skills, equipment, and training necessary to successfully deploy and operationally support each activity or development. The plan shall include expected accomplishment milestones and schedule necessary to successfully turnover responsibility in minimum time. (CDRL 029)

Maintenance Transition Plans shall be delivered on or before 75% of task work is completed, or at a mutually agreed time for Government review and approval.

System Transition Plans shall be delivered in draft at PDR, final 90 days prior to scheduled system delivery or at a mutually agreed time for Government review and approval.

Transition Plan execution and final turnover of responsibility shall be at the discretion of the Government.

4.7 Travel. The Contractor shall include within their proposal, travel costs associated with performance of orders. Proposed travel shall be validated and approved IAW the Joint Travel Regulation (JTR) by the CO prior to issuance of the order.

5.0 Deliverable Data. The contractor shall provide data, documentation, and reports regarding the contract effort.

5.1 Status Reports.

The Contractor shall provide a bi-monthly order status report for all past, present, and planned Task Order / Delivery Order activities for the overall contract effort. (CDRL 001)

The Contractor shall provide a bi-monthly report of all software and database trouble reports submitted (Software Trouble Report). (CDRL 003)

The Contractor shall provide MONTHLY status reports on all items sent to the contractor’s facility for repair, identified by warranty and non-warranty. (CDRL 010)

The Contractor shall provide Bi-MONTLY report status of all trouble solutions, upgrades, enhancements, and sustainment, repair, or warranty work, including work completed, in-progress, scheduled, and not scheduled. (CDRL 012)

The Contractor shall provide a Semi-Annual (every 6 months) inventory report of the Document Archive, by title, date, and originating order. (CDRL 050)

The Contractor shall provide an Annual report of all GFP in possession of the Contractor. The report shall contain property description, model and serial number, and location. The report may be broken down further by task and Government POC. (CDRL 052)

5.2 Capabilities Matrix.

The contractor shall develop and maintain a current capabilities matrix for software enhanced, developed, or maintained under this contract, in particular for ILIAD, ODYSSEY, QLS, and for others as specified in orders.

This matrix shall contain a list of all hardware items supported by ILIAD, both instrumentation and decom, including features supported on each item and contain a list of all software capabilities supported by ILIAD, including import/export formats and catalogs. The list of features to be listed may be expanded in the future.

The contractor shall propose and government approve the Capability Matrix format and contents, with additional content as mutually agreed. Contents of each matrix shall be updated quarterly. (CDRL 009)

5.3 Manuals and Licenses. The contractor shall provide the correct document version for each delivered item type, matching the configuration of the items as delivered.

5.3.1 Reference Documentation. For all hardware, software, or database units or components designed or manufactured by the Contractor or a Subcontractor, the Contractor shall provide reference documentation, describing the unit or component, its configuration, operation, maintenance, and other relevant information.

5.3.2 Manuals. The Contractor shall provide one set of packaged documentation (PD) with each software/hardware item purchased or program licensed (electronic format). All PDs containing proprietary information will be properly marked. The Contractor shall provide PD in searchable electronic format;

hard-copy PD for items delivered under the contract shall be provided upon request. A manual for each individual unit delivered is not necessary, unless otherwise specified in the order. Additional manuals may be required by orders. Additional manuals on media (CD or DVD) are acceptable.

5.3.3 Licensed Programs (Non-Diagnostic). Non-diagnostic programs licenses shall be used subject to the licensing provisions set forth in the Software License Agreement (Exhibit C) of the contract.

5.3.4 Diagnostic Licenses and Products. Diagnostic programs shall be used subject to the licensing provisions set forth in Exhibit C of the contract. Certain items of software provided to the Government by the Contractor use licensed internal code which the Contractor will identify, including any updated or replacement code provided by the Contractor, when supplied by the Contractor with or for a machine.

Diagnostic programs required shall be specified in orders.

5.3.5 Proprietary Licenses. For non-developmental software, the contractor shall license code for use only by the Government, only for the specific machine for which the code is provided designated by serial number or other unique identifier, and only while the Government is the rightful possessor of the machine in accordance with the Software License Agreement of the contract.

5.3.6 Non-Proprietary Licenses.

Software created, enhanced, or developed under this contract shall include unlimited Government Purpose rights to original or source code, and to all additional files and procedures necessary to create running software.

Databases created, enhanced, or developed under this contract shall include unlimited Government Purpose rights to the database schema, structure, all queries and views, and to all additional scripts or code used to manipulate or display the database.

Hardware created, enhanced, or developed under this contract shall include unlimited Government Purpose rights to system design, architecture, implementation details, and specifications.

5.3.7 Developed Software and Source Code Deliverable.

The Contractor shall deliver updated software and applicable source code for software developed or modified under the contract, in electronic format to the Government PM upon delivery. Also include all additional files, environment descriptions, scripts, and procedures required to build the source code release into running software

In addition, the contractor shall provide up to date documentation of all software as delivered, with release notes (and change pages) for minor releases and/or bug fixes, and a fully revised set of documentation for major releases. The contractor shall also identify any other software required to support, maintain, or build the software developed or modified under the contract.

All software developed under this PWS shall be marked with government rights.

All software executables, patches, firmware, and source code, must be delivered in a cybersecure manner, with checksums/hashes delivered via an independent channel. (CDRL 008, 035, 036, 049)

5.3.8 Developed Database and Source Code Deliverable.

The Contractor shall deliver updated databases and applicable descriptions for databases developed or modified under the contract, in electronic format to the Government PM upon delivery. Also include all additional files, environment descriptions, scripts, and procedures required to build the database release into running database.

In addition, the Contractor shall provide up to date documentation of all databases as delivered, with release notes (and change pages) for minor releases and/or bug fixes, and a fully revised set of documentation for major releases. The Contractor shall also identify any other software required to support, maintain, or build the database developed or modified under the contract.

All databases developed under this PWS shall be marked with government rights.

All database scripts, schemas, and configuration data must be delivered in a cybersecure manner, with checksums/hashes delivered via an independent channel. (CDRL 008, 035, 036, 037)

5.4 Engineering Documentation.

For all items on the contract, the Contractor shall manufacture, test, and demonstrate compliance with contract requirements and company processes, and shall deliver the items and documentation required.

The Contractor shall provide the correct document version for each delivered item type, matching the configuration of the items as delivered.

All hardware developed under this PWS shall be marked with government rights. (CDRL 004, 005, 006)

5.4.1 System Engineering Documentation.

Acceptance Test Procedures (ATP) and Acceptance Test Reports (ATR) shall be provided with each delivery. For development orders, Draft ATP shall be delivered at CDR, Final ATP shall be delivered before Acceptance Testing begins. Performance compliance shall be demonstrated by successful completion of the applicable unit ATP as shown in the ATR.

Software Version Descriptions (SVD) shall be provided with each software delivery.

Interface Control Documents (ICD) shall be provided with each software or system delivery.

The Contractor shall propose candidate Hardware Configuration Items (HWCI) and Computer Software Configuration Items (CSCI) to be delivered. Identified Configuration Items shall be documented in the Configuration Baseline, shall be marked with government rights, shall be included in major reviews, and shall be included with the delivery. A Physical Configuration Audit (PCA) shall be performed, and the result included with the delivery.

Requirements traceability for all orders shall be documented, including original requirements and all authorized changes, through to testing and delivery for hardware, software, and database developments.

The documentation shall be available at each major review and at delivery.

All Acceptance Test elements with corresponding Requirements shall be indicated.

All Requirements with corresponding Acceptance Test elements shall be indicated.

(CDRL 022, 023, 024, 025, 026, 027, 004, 005, 006)

5.4.2 Airworthiness Documentation. The Contractor shall support Government airworthiness determination for the target platform when requested. The contractor shall provide Qualification Test Procedures (QTP) and Reports (QTR), Software Version Descriptions (SVD), Interface Control Documents (ICD), all drawings and design documentation and other data for their system as necessary.

The Contractor shall be prepared to comply with the airworthiness criteria found in Mil-Hdbk-516c, and in particular the mechanical, structural, electrical, EMI, workmanship, crash loads, environmental qualification requirements for all equipment intended to be flown on test aircraft.

5.4.3 Cybersecurity Documentation. The Contractor shall support Government cybersecurity determination(s) for the target platform when requested. The contractor shall provide product Supply Chain integrity documentation (hardware and software), Software Version Descriptions (SVD), Interface Control Documents (ICD), computer system design descriptions, data flow descriptions, computer system vulnerability analysis results, computer system vulnerability testing results, data system volatility/non-volatility documentation and other data for their system as necessary.

5.4.4 Software and Database Development Documentation. As required per order, the Contractor shall provide documentation for software and database developments. The Contractor shall consider the Software Development Documents at CDRLs 034 - 049 and shall propose the documents necessary for successful delivery, operation, and maintenance of the software or database. The Contractor shall state reasons for rejecting the others. The Contractor may include other documentation as needed. (CDRL 005, 034 – 049)

5.5 Documentation Maintenance and Archive. The Contractor shall maintain an archive of all source code, database descriptions, manuals, procedures, reports, training, and other documentation generated under the contract. The documents in the archive shall be retrievable upon Government request, and shall be delivered within ten working days of request. Documentation items shall retain their classification as required during both archive and delivery. The Contractor shall report the contents of the archive. (CDRL 050)

5.6 Software and Database Repository. The Contractor shall maintain an online repository that contains the released software and database schemas and all updates, up to date to the most current version, plus archives of all previously released versions. Access to the repository shall be granted to the Government PM, and the Government Technical Points of Contact. (CDRL 008)

6.0 Contract Data Requirements List (CDRLs)

CDRL Title DID Reference / Format

Notes Frequency

001 Delivery/Task Order Status Report

DI-MGMT-80368 Tailored for content Bi-monthly

003 Software Trouble Report DI-MGMT-80368 Tailored for content Bi-monthly 004 Engineering Documentation DI-MISC-80652 briefings, requirements review documentation, design review documentation, verification and validation plans and results, data flow diagrams, software architecture overviews, interface control documents, and other engineering documentation for all new and upgraded capabilities provided in orders

As needed

005 Software Documentation Contractor defined format assemble, maintain, and deliver database or software operation, maintenance, and user documentation and data

As needed

006 Hardware Documentation Contractor defined format assemble maintain, and deliver hardware operation, maintenance, and user documentation and data

As needed

007 Training Materials DI-SESS-81697 None As needed 008 Online Repository Contractor defined format Maintain online repository listing released software and database schemas, and all updates that are up to date to the most current version, plus archives of all previously released versions. Access to the repository shall be granted to the Government PM and Government Technical POCs

Continuous

009 Capabilities Matrix As mutually agreed provide an updated matrix as new capabilities and enhancements are developed

Quarterly

010 Repairs Status Report DI-ILSS-80620 Tailored for content monthly Monthly 011 Teardown Deficiency /

Recommended Repairs Report

DI-ALSS-81534 None As needed

012 Software Work Progress / Work Backlog

DI-MGMT-80368 tailored for content Bi-monthly

013 Maintenance Service Report DI-MGMT-80995A None As needed 020 Meeting Minutes DI-ADMN-81505 None As needed 021 Technical Report DI-MISC-80652 Tailored to N/A DID para 7.2 and 7.3, 10.2 e-format is acceptable

As needed

022 Qualification Test Procedure DI-ATTS-80282B None As needed 023 Qualification Test Report DI-ATTS-80282B Tailored to include test data, results and conclusions.

024 Acceptance Test Procedure DI-RELI-80322 None As needed 025 Acceptance Test Report DI-RELI-80322 tailored to include test data, results and conclusions

026 Software Version Description DI-IPSC-81442A None As needed

027 Interface Control Document DI-SESS-81248B tailored to include specified content As needed 028 O&M Manuals & Instructions DI-MISC-81414 None As needed 029 Transition & Turnover Plan As mutually agreed None As needed 034 Interface Requirements

Specification DI IPSC 81434A None As needed

035 Software Design Description DI IPSC 81435A *See Note As needed 036 Interface Design Description DI IPSC 81436A *See Note As needed 037 Database Design Description DI IPSC 81437A *See Note As needed 038 Software Test Plan DI IPSC 81438A None As needed 039 Software Test Description DI IPSC 81439A None As needed 043 Software User Manual DI IPSC 81443A None As needed 047 Computer Programming

Manual DI IPSC 81447A None As needed

048 Software Programmer’s Guide

DI IPSC 81633 None As needed

049 Computer Software Product DI IPSC 81488 *See Note As needed 050 Document Archive Content

Inventory As mutually agreed None Semi-Annual

052 GFP inventory As mutually agreed None Annual

* Note: Software Development Documents. Source code provided shall be in accordance with PWS paragraphs 3 and 4 as specified on orders. The source code shall be delivered electronically with all required libraries, build scripts, compiler specifications, and directions to compile the code into a usable product. This source code will be accessible to authorized users from government computers. The contractor shall also maintain an online software status report that identifies the work in progress and change logs to the code, updated at the end of each business day.

7.0 Ordering Procedures.

Orders will be issued against the basic contract and will be executed IAW the basic contract’s terms, conditions, PWS, and each individual order’s Statement of Objectives (SOO) and any other items identified. The CO will issue an RFP to the Contractor describing the requirements for each order. In response to the RFP, the Contractor shall submit a proposal to include all applicable documentation for review by the CO. The Contractor shall provide technical, resource, price, schedule proposal and data in support of the contemplated order to include a Technical Statement of Work (TSOW). If necessary, the CO will schedule negotiations with the Contractor and at the conclusion of successful negotiations, award an individual firm-fixed-price (FFP) order.

The response time for a proposal shall be 10 business days after receipt of the RFP. Due to mission requirements, it may be necessary to require the Contractor’s proposal in less than 10 business days after receipt of the RFP. For more complex projects, additional time may be granted by the CO. For each order, the Contractor shall submit a proposal utilizing the contract’s Pricing Schedule.

All orders will be FFP and negotiated on a line item by line item basis. Pricing established for the basic contract shall include pricing for all five years of the contract and will be utilized throughout contract performance. Negotiations will establish the appropriate line items for the order and quantities for each line item. The Contractor must be prepared to provide quantity calculations justifying the quantities contained in the proposal. At the conclusion of negotiations, the CO will negotiate a reasonable and expeditious performance period based upon input from the PM.

8.0 Order Pricing

Exhibit B shall include pre-priced, products and labor rates. The agreed upon prices will then be used as the basis for order pricing for all orders issued against the contract. The Pricing Schedule will be attached to the awarded contract as Exhibit B and shall be used for the life of the contract. Any changes made to Exhibit B can only be made by authority of the CO and will be incorporated into the contract via a modification to the basic contract.

The Contractor’s pricing shall account for a wide variety of risks of doing business including, but not limited to, overhead and profit, minimum design costs, administrative and technical support, General and Administrative (G&A) expenses, insurance, taxes, licenses and fees, waste and excess materials, compliance with environmental and safety laws, project management, scoping meetings with Government personnel, and a variety of other overhead costs items.

Non Pre-priced Items. Costs for products or services not listed on Exhibit B, and within the scope and general intent of the contract, must be submitted by the Contractor as specified within this PWS, and approved by the CO to be incorporated into Exhibit B via a contract modification. Addition of new products/labor categories to the Pricing Schedule can only be done after successful negotiations for the item and via modification to the basic contract by the CO.

9.0 Service Delivery Summary (SDS). The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objective PWS Paragraph

Performance Threshold

Products. Provide price quotations, hardware and software products as listed in the product price list, install and start up products as required.

3 Price quotations are accurate according to the price list 95% of the time.

Product deliveries are timely 90% of the time.

Product installation and start-up are timely 90% of the time.

Services. Provide price quotations, provide services as described in orders, install and start up systems, transition systems as required.

Risks. High Risk concerns are reported as required.

4.0 Price quotations are accurate according to the price

list 95% of the time.

100% of high risk concerns are reported timely.

Maintenance Services. Emergency and routine maintenance is completed. All system and equipment components are free of defects, errors, and problems. Service calls are handled appropriately within the specified timeframe.

Users are satisfied with service call performance.

4.1 Completion of routine task activities and orders are

timely 90% of the time.

Completion of emergency task activities and orders are timely 95% of the time

System Enhancement & Development. Provide support services, software development, system engineering, software licenses, and support documentation

System Engineering. Demonstrate best practices of system engineering Technical Processes and Technical Activities.

Software Engineering. Demonstrate Software Development Life Cycle compliance. Identify development methods.

4.2 Major task events and deliveries are completed as

scheduled and as specified in the order 90% of the time.

Major task events and delivery changes are documented in advance of the scheduled event date 90% of the time.

System engineering Technical Process and Technical Activity results are acceptable quality 95% of the time.

100% of SDLC is standards compliant.

100% of development methods identified.

Training. Provide training as specified in tasks. 4.3 Training events are completed timely and as scheduled and as specified in the order 90% of the time.

Knowledge Management. Provide knowledge management, data analysis and data reporting as required in orders.

4.4 Completion of routine task activities and orders are

timely 90% of the time.

Cybersecurity. Deliveries are secure.

Inspections are completed and documented before installation.

4.5 100% of deliveries are delivered securely.

100% of inspections are completed and documented before installation.

Transitions and Turnovers. Maintenance Transition Plans delivered on or before 75% of order is completed.

System Transition Plans draft delivered at PDR, final delivered as required.

4.6 Plans produced and delivered timely 90% of the

time.

Status Reports 5.1 Status reports are submitted timely 95% of the time.

Manuals and Licenses. All documents are submitted on time, accurate and contain all applicable data.

5.3 Documents are submitted timely 95% of the time.

Document Maintenance and Archive.