EQASP SME SOW Final 10142020.docx

ELECTRONIC QUALITY ASSURANCE SURVEILLANCE PLAN (E-QASP)

SOFTWARE IT SYSTEM SME SUPPORT

STATEMENT OF WORK

Contractor shall deliver Subject Matter System support in the development of a functional Electronic Quality Assurance Sustainment Plan (E-QASP).

1) The E-QASP Shall:

Be based on Aerospace Industry Standard AS9100D (or latest version) Quality Management System (QMS) processes to ensure enterprise wide standardization for documenting contractor nonconformance findings during Contractor Officer Representative (COR) surveillance/audit reporting through the use of charts and numerical values. The system shall utilize rating systems similar to the AS9100D to provide quantifiable data which is easily translatable for use with internal/external AS9100D quality management systems.

2) REGULATORY GUIDANCE:

Contractor SME shall work with Government development team to ensure DFARS 246.470-2 Quality Evaluation Data standards are built into the E-QASP system for the collection, evaluation, and use of the types of quality evaluation data specified in PGI 246.470 GCQA, and PGI 246.470-2. Contractor Quality Performance Evaluation Data includes: Contractor Quality Performance Data that is captured during Contractor Quality Assurance Surveillance/Audits, Service Summaries, Second Party Audits, provided Contractor Data, and any applicable data/reports by Users and Customers. Identification of all work requiring contractor surveillance shall use the DFARS 246.470.2 method of surveillance IAW (FAR 46.401).

3) E-QASP SYSTEM SUBJECT MATTER EXPERT (SME) REQUIREMENTS:

Contractor shall provide Subject Matter Expert support during the period of E-QASP system development. Contractor shall provide support in development of system functionality and user experience requirements

1. Individual should be familiar with JPO COR surveillance and auditing operations and procedures and have E-QASP specific system development experience

4) E-QASP SYSTEM REQUIREMENTS:

SME shall provide support in development of an electronic Quality Surveillance Plan(E-QASP) consisting of the following functionality requirements:

1. QASPs shall consist of categories (CLINS/PWS/SOW) based on F-35 Contracts

i. Categories will consist of applicable surveillance checklists

2. QASPs shall be versioned to ensure a complete trail of data and to prevent corruption of the historical data

3. Administer existing QASPs

4. Modify and delete or generate new QASPs

5. Control access to QASPs

6. Utilize QASPs at multiple locations specified by contract

7. Allow access to QASPs from government approved devices

8. Provide tools for analysis and trending of historical data gathered by QASPs

9. Data will be aggregated based on region, depot/base, specific items requested

10. Data can be aggregated between all regions

11. Analysis shall include

i. Trend data displayed visually or in table format

ii. Ability to filter results by category or chronologically

iii. Ability to print or download graphics and tables

12. Export specified data from QASPs

5) CONTRACTOR OFFICER REPRESENTATIVE (COR) COR USER ACTIONS:

COR actions specific to Users (Approx 50-100):

1. COR Actions can only be created, modified, deleted by registered COR (i.e: no external corruption of data)

2. Actions will be indexed and searchable

3. Data will be provided to CORs with access rights approved only by COR Lead

4. Automatic COR QASP report generation tailored to dollar value and complexity of specific contract CLIN requirements, task or delivery order under contract, i.e., monthly contractor performance surveillance and audit reports as defined by FAR Inspection of Services Clause FAR 52.2464 and DODI Instr 5000.72

6) E-QASP SYSTEM ADMINISTRATION TOOLS:

E-QASP administrative rights shall be responsibility of COR Lead for management of:

1. User Approvals

2. Account Creation, Modification, Deletion

3. User access approval can be assigned or removed from user accounts

4. Two-Factor authentication for Login

5. Ability to reset password autonomously

6. Assign user to a region or station

7. System shall be available at all hours during the unless scheduled maintenance has been coordinated and announced. Maintenance of site shall be coordinated and approved by the COR or CO.

8. Administrators will be able to pull reports between requested dates

9. Administrators will be able to schedule recurring reports to be generated Contractor shall provide development assistance to ensure development requirements meet or exceed the following accessibility requirements. The system must be able to support multiple points of simultaneous access. Furthermore, the Lead COR will approve or disapprove user accounts. Additionally, the system shall be accessible on any U.S approved Government device. Therefore, Microsoft Visual Basic and programming using universal programming languages is required. The Lead COR has rights to obtain monthly reports, and ability to update permissions immediately. System shall be ready for immediate delivery upon award in a fully-functioning format.

7) SOURCE CODE:

All Source Code developed for E-QASP will be the property of JPO.

8) USER INTERFACE:

Contractor shall assist government developers to ensure high attention paid to user interface for ease of use.

System shall use colors/schemes/backgrounds and user controls logically sequenced or placed. The data base shall be able to be used to produce charts, graphs, trend analysis, comparison data from site to site, able to save large amounts of information for recall, have the ability to immediately retrieve information, and have the ability to e-mail information.

9) TRAVEL:

Contractor shall be required to travel to Hill AFB as required to meet with government personnel to support development and implementation of the E-QASP.