SAI SIR Section J.5 12.27.23.docx

Attachment J.5 12/27/2023 Data Item Descriptions

DATA ITEM DESCRIPTION

1. TITLE

Integrated Master Schedule

2. NUMBER

PM01-IMS

3. DESCRIPTION/PURPOSE

The Integrated Master Schedule is used to plan, manage, and control all program activities throughout the required reporting period.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.1.2 Format: Contractor format is acceptable Contents: The IMS must identify all contract deliverables and critical milestones (including applicable support activities) to meet SAI program activities defined in the Section C, SAI Performance Work Statement (PWS), and Section F, Deliveries or Performance.

Key Elements of Detailed Schedules. The key elements of the detailed schedules include the following:

1. Task/Activity. An element of work with duration.

2. Milestone. A specific definable accomplishment in the contract network, recognizable at a particular point in time. Milestones have zero duration and do not consume resources.

3. Duration. The length of time estimated (or realized) to accomplish a task/activity.

4. Percent Complete (Schedule). The proportion of an activity or task that has been completed to a point in time.

DATA ITEM DESCRIPTION

1. TITLE

User Manual (UM)

2. NUMBER

PM02-UM

3. DESCRIPTION/PURPOSE

The SAI User Manual provides the information necessary for end users to effectively use the SAI solution.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.3

1. General instructions.

Substitution of existing documents: Commercial or other existing documents may be substituted for all or part of the document if they contain the required data.

2. Format Contractor format is acceptable.

3. Content. The manual shall contain the following:

a. Title page or identifier. The document shall include a title page containing, as applicable: document number; volume number; version/revision indicator; security markings or other restrictions on the handling of the document; date; document title; name, abbreviation, and any other identifier for the system, subsystem, or item to which the document applies

b. Table of contents and index. The document shall contain a table of contents providing the number, title, and page number of each titled paragraph, figure, table, and appendix, and an index providing an alphabetic listing of key terms and concepts covered in the document and the pages or paragraphs in which the terms or concepts are covered.

c. Page numbering/labeling. Each page shall contain a unique page number Content should include the following:

1. Introduction

1.1 Overview: This paragraph shall briefly state the purpose of the solution to which this document applies. It shall describe the general nature of the system and software; summarize the operation, and maintenance

2. System Overview: Provide a general overview of the system from initiation through exit. The logical arrangement of the information should enable the user to understand the sequence and flow of the system. This section should include, but nor be limited to the following:

2.1 Cautions & Warnings

2.2 Set-up Considerations

2.3 User Access Considerations

2.4 Accessing the System

2.5 System Organization & Navigation

2.6 Exiting the System

3. Using the System: Provide a detailed description of each user function and/or feature, explaining in detail the characteristics of the required input and system-produced output. Each function/feature should be described under a separate sub-section header and should correspond sequentially to the system functions (e.g., menu items) and/or features listed in certain sub-sections found in this document. Include screen prints as needed to depict examples. This section of the User Manual may also be tailored or customized based on defined user roles, if appropriate.

3.1 <Given Function/Feature>

3.1.1 <Given Sub-Function/Sub-Feature>

4. Fault Conditions: Describe fault conditions, including error conditions that may be generated and corrective actions that may need to be taken. The following are common sub-sections that may be included as appropriate:

DATA ITEM DESCRIPTION

1. TITLE

Service Requalification Test Plan

2. NUMBER

TE01-SRQ Test Plan

3. DESCRIPTION/PURPOSE

The Service Requalification Test Plan provides Contractor’s overall test philosophy, test definition and detailed planning information for tests to be conducted by the Contractor if a modification to the service baseline is required that impacts any of the requirements defined in Attachment J-1 Minimum Requirements Document (MRD).

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.6 Format and Contents:

Format: Contractor format is acceptable.

Content:

· The SRQ Test Plan must include test sections for each test procedure to be developed. Information must be provided to the level necessary to show adequacy of the proposed test methods, test philosophy, and success criteria for verification of requirements. Specific methods for performance measurement and data reduction and analysis (DR&A) must be included. In addition, a matrix to identify the test procedure wherein each allocated requirement is planned to be addressed.

· The SRQ Test Plan must delineate how required tests, necessary to address validation of the Contractor’s and Government’s specified requirements, support the overall test program to be conducted by the Contractor: the proposed test methodologies that address the requirements as allocated to each test; and input types, test/data reduction and analysis tools, certifications, accreditations, controls, and the overall processes (e.g. certification, inspection, validation, quality, and etc.) needed to address the complete scope of testing.

The Test Plan must include, at a minimum:

DATA ITEM DESCRIPTION

1. TITLE

Service Requalification Test Procedures (SRQTP)

2. NUMBER

TE02-SRQTP

3. DESCRIPTION/PURPOSE

1. The SRQTP documents the detailed step-by-step instructions to be followed during Contractor-conducted testing.

2. A separate SRQTP must be prepared for each required test activity.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.6 Format and Contents:

Format: Contractor format is acceptable.

The test procedure must include the step-by-step detailed procedures and background information required to verify requirements identified in the Test Plan. The test procedure must include, at a minimum, the following:

1. Title Page. The title page must uniquely identify the individual test, the contract item(s) to be tested, and the primary functions or segments to be tested.

2. Test Objective. Include references to the SAI MRD, requirements to be verified as they occur in the various procedural sections and at the appropriate point of verification.

3. Location and Schedule. The location, schedule and expected duration must be provided for pre-test readiness briefings, test conduct, data reduction and analysis efforts, and post-test TIM debriefings.

4. References. Reference documents applicable to the test must be listed. Such references must include:

a. Specification for the functions to be tested

b. Users’ manuals for the equipment and/or software

c. Users’ manuals for test and support computer program and equipment

5. Personnel and Responsibilities. Requirements and responsibilities must be provided for all essential test personnel. Responsibilities of individual contractors or agencies for supplying personnel must be provided.

6. System Configuration Description. A description of the test article including the test configuration must be provided.

7. Test Support Tools and Equipment. Specific identification of test support equipment and software (e.g. scenarios, tools, drivers, Data Reduction and Analysis software, etc.) necessary to support the test must be specified. The manufacturer and model number must be specified for all test support equipment. Manufacturer and release level must be specified for all test support software.

8. Prerequisites. This section must identify tests required to be completed as well as the support documentation, and the initial test bed conditions required to start the test.

9. Detailed Test Description. The Test Description must describe in detail how each test must verify requirements.

10. Test Input. This section must describe in detail all test inputs necessary to conduct the test. All sources used to generate the test inputs must be specified.

11. Test Operating Procedures. Detailed step-by-step procedures for conducting the test as well as expected results must be specified in this section. Procedural steps must be described in the order in which they are planned to occur with dependency of any one step on another so indicated. If more than one operating or monitoring position is involved in the test, the sequence of events for each position must be indicated. Interdependence of operating positions with respect to specific events must be described.

12. Data Reduction & Analysis (DR&A). This section must contain the requirements and procedures for reduction and analysis of test data. The information must be contained in subsections as follows.

a. Recording and Reduction Requirements. Data which must be recorded during the test by the program, manually and/or by instrumentation, shall be specified. In addition, requirements for format and content of the data resulting from the reduction/analysis process must be specified. Requirements for data recording and reduction must be specified in a manner and detail such that the resulting information will clearly show whether the test objectives have been met.

b. Data Reduction/Analysis Procedures. This subsection shall contain the procedures to be employed in reducing and analyzing data resulting from the test.

Appendix A - Test Log. This section must include a template to capture test log records for all test runs. This section must include the approach for recording test actions, summaries, and failure information and corrective action (if applicable) during any test run. The test log template must contain the following at a minimum:

DATA ITEM DESCRIPTION

1. TITLE

Service Requalification Test Report (SRQTR)

2. NUMBER

TE03-SRQTR

3. DESCRIPTION/PURPOSE

The Test Report documents the results of a requalification test and the subsequent data analysis.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.6 Format and Contents:

Format: Contractor format is acceptable.

Content: The test report must provide the results of formal test and subsequent data analysis. The Test Report must include, at a minimum the following:

1. Title Page. The title page must uniquely identify the individual test, the contract item or item tested, and the primary functions or segments tested.

2. Test Objective. The specific test objective, including reference to the requirements designated for this test.

3. References. The reference to the applicable Test Procedures.

4. Test Description. A general description of the test article that:

a. Identifies whether a full or partial system configuration was utilized (if partial, identify specific parts included or left out, whichever is shorter, along with rationale for using partial configuration).

b. Identifies quantity of site configurable components utilized in test configuration.

c. Includes test configuration diagram(s).

d. Identifies location of the test article (i.e. factory, on-site).

5. Test Equipment. A list of all test equipment, including manufacturer, model, calibration status, and serial number. Reference may be made to the applicable Test Log entry numbers.

6. Test Tools. A list of all system, test, and Data Reduction and Analysis (DR&A) software and adaptation utilized, identifying title, release level, and release date.

7. Test Approach. A description of the test approach and success criteria utilized to verify each requirement tested. Red-lines (if any) introduced during test execution must be accounted for in these descriptions.

8. Test Matrix. A test matrix that provides a summary of test results, which contains the following information for each requirement tested in this event:

9. Regression Testing. Provide a complete description of any planned or actual regression test activities as a result of PTRs generated during execution of this test event due to test failures or other noted system anomalies. This description must include reference to the specific test case, section, and steps that need to be executed from the test procedure or indicate that new or additional steps must be generated to address the PTR.

10. Action Items Matrix. Include a matrix that identifies any Action Items (AIs) that have been generated as a result of this test event during:

11. Test Results. Detailed test results, including the items listed below must be provided:

12. Program Trouble Reports (PTRs). For each step of a test procedure where a problem occurred, identify the procedure step number, and the expected impact of the problem on the validity of preceding or following steps of the test procedure. Amplifying information (for example: diagrams) should be included. Reference may be made to the applicable PTR(s) listing the number and brief description. A copy of the PTR must be included as an appendix to this report.

13. Data Analysis. Detailed data analysis results and a complete description of post-test data analysis activities must be provided and linked with the plan and procedure sections which generated the “raw” data input, and the DR&A test procedures which produced the resultant output.

14. Test Evaluation. An overall analysis of the functional performance of the article tested must be provided. This analysis must describe the functional capability as it was demonstrated in the test, noting any specific deficiencies (making reference to PTRs) that were discovered. Other test events must be identified that address each requirement that is only partially allocated to this test.

15. Test Results Witness Signatures. The names and signatures of Contractor and Government personnel present during the test.

DATA ITEM DESCRIPTION

1. TITLE

Technical Performance Measures Report (TPMR)

2. NUMBER

SM01- TPMR

3. DESCRIPTION/PURPOSE

This Technical Performance Measures Report (TPMR) summarizes the performance of the SAI solution at each site during the reporting period. The TPMR will provide the FAA with an accurate, consistent, timely, and readily understandable summary assessment of TPMs in Attachment J-7 against the applicable requirements in Attachment J.1 MRD.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.8.2 Format and Contents:

Format: Contractor format is acceptable. Where information is presented at the service or facility level, the data must also be provided in a standard format that allows the Government to import the information into a spreadsheet or database for query purposes.

Contents: The Technical Measures Performance Report must contain the following information at a minimum:

1. Executive Summary.

a. The section must identify the site by name.

b. Highlights of the past month’s performance;

c. Any performance issues that should be brought to the FAA’s attention; and

d. Cause of performance issues and recommended remedial actions.

2. Technical Performance Measures Summary for SAI Services. This section of the report must provide a summary of service performance.

a. Update rate

b. Latency

c. Adjusted Service Availability (as defined in Attachment J-1)

i. 1-month Adjusted Service Availability with an indication of whether the Adjusted Service Availability is lower, higher or the same compared to the previous reporting period;

ii. Previous 12-month Adjusted Service Availability;

iii. Number of outages and their duration during the reporting period;

iv. Number of outages and their duration during the most recent 12 reporting periods;

v. Contractor’s assessment and justification of excused outages.

DATA ITEM DESCRIPTION

1. TITLE

Maintenance Plan (MP)

2. NUMBER

SM02-MP

3. DESCRIPTION/PURPOSE

This Maintenance Plan identifies the Contractor’s maintenance organization(s) and describes the approach, processes, and procedures to be used to successfully maintain the system components that comprise the SAI solution.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.8.3 Format and Contents:

Format: Contractor format is acceptable.

Contents: The Maintenance Plan must contain the following information at a minimum:

DATA ITEM DESCRIPTION

1. TITLE

Design Site Survey (DSS) Report

2. NUMBER

IM01-DSSR

3. DESCRIPTION/PURPOSE

The Design Site Survey Report (DSSR) is required to document the results of the Site Survey for each site and must be used to determine the preparations required for system installation, test, and Government acceptance. The DSSR information will be utilized to develop the Site-Specific Implementation Plan (SSIP) SAI IM-SSIP. If applicable the report will also document preparations required for site remediation, site restoration, equipment removal and disposition.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.9.2 Format and Contents:

a) Executive Summary. The DSSR must contain a summary of the site survey observations, SAI equipment requirements and summary of site preparation activities required to install SAI equipment. If applicable, DSSR must contain a summary of preparations required for site remediation, site restoration, equipment removal and disposition.

5. Appendix: The DSSR must include results of a site Radio Path Analysis and Coverage Analysis.

DATA ITEM DESCRIPTION

1. TITLE

Site-Specific Implementation Plan (SSIP)

2. NUMBER

IM02- SSIP

3. DESCRIPTION/PURPOSE

The Site-Specific Implementation Plan (SSIP) describes the plan for implementing the SAI solution at a specific facility. The SSIP identifies implementation elements including proposed equipment locations, cable runs, required power and grounding connections. The SSIP identifies the specific activities and projected timeline for the implementation of the SAI solution at a specific facility through completion of service acceptance testing

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.9.3 Format and Contents: Contractor format is acceptable Contents: The Site-Specific Implementation Plan (SSIP) must contain the following information at a minimum:

DATA ITEM DESCRIPTION

1. TITLE

Service Acceptance Test (SAT) Procedures

2. NUMBER

IM03 – SATP

3. DESCRIPTION/PURPOSE

The SATP documents the detailed step-by-step instructions to be followed during Contractor-conducted SAT, an end-to-end solution verification test to validate the SAI solution’s site operation and performance.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.9.6 Format and Contents:

Format: Contractor format is acceptable.

Contents: The Service Acceptance Test Procedures must contain the following information at a minimum:

1. Title Page. The title page must contain the following at a minimum:

a. SAI Service Acceptance Test Procedures;

b. Signatures from the SAI Contractor Test Manager and the Government Test Director;

c. Submittal date; and

d. Version number

e. Site identified by name.

2. Test Description.

DATA ITEM DESCRIPTION

1. TITLE

Service Acceptance Test Report (SATR)

2. NUMBER

IM04 – SATR

3. DESCRIPTION/PURPOSE

The Test Report documents the results of the Service Acceptance Test and the subsequent data analysis.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.9.6 Format: Contractor format is acceptable. When attachments are included, they shall be fully identified, referenced in the text, and folded to conform to the size paper used in the report.

Content: The test report must provide the results of the formal test and subsequent data analysis. The Test Report must include, at a minimum the following:

1. Site identified by name.

2. The scope of the report in terms of time and activities covered.

3. The purpose of the test and specific test objective, including reference to the applicable Test Matrix designated for this test.

4. Reference to Service Test Procedure.

5. The description of the test article including test configuration. A list of all system, test, and software utilized identifying title, release level, and release date.

6. A list of all test equipment, including manufacturer, model, calibration status, and serial number. Reference may be made to the applicable test procedure sections or the official Test Log, Log Entry #s, and Log pages.

7. Description of the criteria used for the verification of each requirement tested.

8. A summary of test results. Include a test matrix identifying test procedure section and the applicable Test Requirement Matrix success criteria to be met.

9. Identify any item remaining open after completion of test conduct and analysis from: Log Book Entries, test matrix deficiencies. Generate trouble reports or each item, listing the number(s)/brief description herein, and attach a copy of each trouble report as an appendix to this report.

10. Detailed Test Results. List the results of the test based on the data collected during the test.

11. Detail Data Analysis. Detailed data analysis results and a complete description of post-test data analysis activities shall be provided and linked with the appropriate procedure sections.

12. Test Evaluation. An overall analysis of the functional performance of the SAI solution. The analysis shall describe the operational and functional capability as was demonstrated in the test.

13. The test report shall contain a certification that the test results are authentic, accurate, current, and in accordance with related requirements and test plans. Include names of Contractor and Government personnel present during the test.

DATA ITEM DESCRIPTION

1. TITLE

Contractor Acceptance Checklist (CAC)

2. NUMBER

IM05 – CAC

3. DESCRIPTION/PURPOSE

The CAC is to ensure that the SAI solution was successfully installed, tested, and shown to meet applicable contract requirements. This DID is for the development of a checklist to be filled out for site acceptance and submitted with IMP06-ADP.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.9.7 Format and Contents:

Format: Contractor format is acceptable. Word processing must be accomplished using Microsoft Word, Microsoft Excel, and/or Microsoft Power Point.

Contents. The facility (site) walk-through inspection checklist shall include, but not limited to, the following type of information as applicable:

· Date of report.

· Site identified by name

· All construction equipment, trash and foreign object debris removed from site. Any HAZMAT disposed of in accordance with local regulations. Disposition report available to be included with CAI report.

· Foundation, building(s), towers/poles, antenna systems, obstruction marking/lighting, ladders/steps/railing, and other physical structures completed

· Lightning protection - Earth Electrode System (EES) installed per design plans/specifications, all exterior structures, conduits and electrical boxes grounded to EES.

· Electrical wiring between utility company transformer/switchgear and site, metering equipment and facility service disconnect installed according to local regulations and inspected by the local utility company.

· Electrical equipment placement is within protective allowances

· All single-point and multi-point grounding, bonding and shielding of electrical equipment inside the facility is completed per NEFAA-STD-019F and/or local regulations

· All safety equipment labels are installed on exterior and interior equipment and electrical panels

· Electrical panel schedules are placed on the door inside electrical panels

· Electrical wiring inside the facility installed per design plans with any deviations depicted on red line set of drawings. Red line drawings clearly depict circuit breaker numbering for electrical circuits running in conduits and terminated at electrical equipment, switches and receptacles.

· Contractor Remote Monitoring Service

· Telecommunications conduits, cables, patch panels and other telco equipment outside and inside the Government facility is installed per design plans and clearly labeled, with any deviations depicted on red-line set of drawings

· Punch List if applicable, and recommended dates of completion for Punch List items

· List of Deficiencies/Exceptions, and remediation plan

· Updated (red-lined) facility drawings completed

DATA ITEM DESCRIPTION

1. TITLE

Acceptance Data Package (ADP)

2. NUMBER

IM06 – ADP

3. DESCRIPTION/PURPOSE

The ADP provides the final documentation of the preparation, installation, and associated services and activities performed to successfully complete the acceptance requirements for the SAI solution.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.9.7 Format and Contents:

FORMAT. Contractor format is acceptable, except it must conform to the specific directions below CONTENTS. The ADP package must contain, but is not limited to, the following:

· Service Acceptance Test (SAT) Report. Completed SAT Report, including test results and any checklists, to provide evidence that the system meets the SAI MRD (Attachment J.1) and Performance Work Statement (PWS), and demonstrate that the system was installed IAW site design drawings and specifications. The SAT Report also needs to include a complete assessment of the system operational performance, based on data collected during on-site tests.

· Contractor Acceptance Checklist. Completed CAC SAI-IM05 to ensure that the installation is complete and meets requirements of the SAI MRD (Attachment J.1) and the Performance Work Statement (PWS). Any findings of deficiencies must be documented.

· Documentation of the hardware and software configuration of the installed system components as tested, including an inventory and identification of all units and line replaceable units (LRU) installed.

· Red-Lined Drawings. One complete set of facility drawings red-lined during the installation process.

· The contractor must certify that the system, as installed, meets all specifications and operational performance requirements, to obtain Government acceptance. The acceptance must also include the completed CAC and List of Deficiencies/Exceptions, i.e. items that deviate from the required installation as annotated during SAT and Contractor Acceptance. The items identified as deficiencies must be resolved or have solid plan/date for remediation prior to system acceptance, unless agreed upon by the Government Team.