About this file

Section J-3 DID (pdf)

View the file

Other files

File Type Posted
Section J-10 Equipment Inventory Lists.xls XLS spreadsheet
Section A.pdf PDF
TSS Questions and Answers_Amendment 000003.pdf PDF
Section J-11 Ground Objects.pdf PDF
Section J-4 TSS Locations.pdf PDF
Section J-7 Mobile Unit Configuration.pdf PDF
Section J-5 TSS Configurations.pdf PDF
Section G.pdf PDF
Section E.pdf PDF
Section A_DTFAWA-17-R-00029 Amendment 000003.pdf PDF
Section C_ Amendment 000002.pdf PDF
Section I.pdf PDF
Section J- List of Attachments.pdf PDF
Section J-2 CDRL.pdf PDF
TSS Questions and Answers_Amendment 000002.pdf PDF
Section L_Amendment 000003.pdf PDF
Section J-9 - Vehicle Fleet List.pdf PDF
Section B_Amendment 000003.xlsx XLSX spreadsheet
Section J-8 Test Bed and Depot System Configuration.pdf PDF
Section K.pdf PDF
Section J-6 TSS Pseudo Pilot Amendment_000003.pdf PDF
Section L-2.pdf PDF
Section L-1.pdf PDF
Section A_ DTFAWA-17-R-00029 Amendment 000002.pdf PDF
Section H.pdf PDF
Section J-1 TSS Specification.pdf PDF
Section F.pdf PDF
Section M_Amendment 000003.pdf PDF
Section D.pdf PDF
Section A_Amendment 000001.pdf PDF
Section J-6 Pseudo Pilot Configuration.pdf PDF
Section D.pdf PDF
Section J-1 TSS Specification.pdf PDF
Section L-1.pdf PDF
Section J-8 Test Bed and Depot System Configuration.pdf PDF
Section A_ DTFAWA-17-R-00029 Amendment 000002.pdf PDF
Section A.pdf PDF
Section I.pdf PDF
Section K.pdf PDF
Section J-4 TSS Locations.pdf PDF
Section J-2 CDRL.pdf PDF
Section J-5 TSS Configurations.pdf PDF
Section E.pdf PDF
Section J- List of Attachments.pdf PDF
Section J-9 - Vehicle Fleet List.pdf PDF
Section H.pdf PDF
Section J-7 Mobile Unit Configuration.pdf PDF
Section G.pdf PDF
Section J-3 DID.pdf PDF
Section F.pdf PDF
Show 40 more

Latest 50 of 165 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Tower Simulation System

(TSS)

Contract Data Item Descriptions (DID) v0.14

May 3, 2017

DTFAWA-17-R-00029

Attachment J-3

CONTRACT Data Item Descriptions (DIDs)

CDRL Number DID Name DID Number

Program Documents

A001 Program Management Plan (PMP) DI-FAA-TSS-PM-001

A002 Monthly Program Status Report DI-FAA-TSS-PM-002

A003 Contractor Support Transition Plan DI-FAA-TSS-PM-003

A004 Meeting Agenda DI-FAA-TSS-PM-004

A005 Meeting Minutes DI-FAA-TSS-PM-005

A006 Reserved

Configuration Management Documents

A007 Configuration Management Plan (CMP) DI-FAA-TSS-CM-001

A008 Request For Deviation / Waiver DI-FAA-TSS-CM-002

A009 Specification Change Notice DI-FAA-TSS-CM-003

A010 Engineering Change Proposal (ECP) DI-FAA-TSS-CM-004

A011 Contract Change Proposal DI-FAA-TSS-CM-005

Logistics Support Documents

A012 Integrated Logistics Support Plan (ILSP) DI-FAA-TSS-ILS-001

A013 Obsolete Parts Report DI-FAA-TSS-ILS-002

A014 Recommended Site Spares List DI-FAA-TSS-ILS-003

Site Documents

A015 Site Survey Plan DI-FAA-TSS-ENG-001

A016 Site Notification Letter DI-FAA-TSS-ENG-002

A017 Facility Design Criteria DI-FAA-TSS-ENG-003

A018 Site Survey In-Brief DI-FAA-TSS-ENG-004

A019 Site Survey Report DI-FAA-TSS-ENG-005

A020 Site Installation Drawings DI-FAA-TSS-ENG-006

Test Documents

A021 Test Plan - Factory Acceptance Test (FAT) Plan DI-FAA-TSS-TEST-001

A022 Test Procedures – FAT Procedures DI-FAA-TSS-TEST-002

A023 Test Report – FAT Report DI-FAA-TSS-TEST-003

A024 Reserved

A025 Reserved

CONTRACT Data Item Descriptions (DIDs)

CDRL Number DID Name DID Number

Test Documents (Continued)

A026 Test Plan - Site Installation Verification (SIV) Test Plan DI-FAA-TSS-Test-001

A027 Test Procedures – SIV Procedures DI-FAA-TSS-Test-002

A028 Test Report – SIV Report DI-FAA-TSS-TEST-003

Training Documents

A029 Training Materials DI-FAA-TSS-ILS-004

A030 Reserved

A031 Reserved

Technical Documents

A032 Visual Database Design Document (VDDD) DI-FAA-TSS-ENG-007

A033 Engineering Services Request (ESR) DI-FAA-TSS-ENG-008

A034 Engineering and Technical Services Report (ETSR) DI-FAA-TSS-ENG-009

DATA ITEM DESCRIPTION (DID)

1. Title

Program Management Plan (PMP), A001

2. Identification Number

DI-FAA-TSS-PM-001

3. Description/Purpose

The PMP describes the Contractor’s management organization to include interrelationships between the prime contractor, major subcontractors and the FAA. The PMP is an inclusive management plan providing details of the specific techniques, tasks, processes and procedures to be used for monitoring performance, contract management, schedule management, resource planning, risk management, quality management, configuration management, data management, security and cost control.

4. Approval Date (YYYY/MM/DD)

N/A

5. Office of Primary Responsibility (OPR)

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

N/A

7. Application/Interrelationship

This data item description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the TSS contract.

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

10. Preparation Instructions

FORMAT and CONTENT. Contractor format is acceptable. The PMP must contain an overview of the

Contractor’s management approach to program, technical, schedule, performance, and cost control; authority of the Contractor’s Program Manager, and the relationship of the PMP to other programmatic policies, procedures, and planning documents; and methods of incorporating changes into the PMP. The PMP must also show how the

Contractor will incorporate their internally approved processes and procedures into the management of this contract and must include, but is not limited to, the following sections:

A. Management Organization. This section must include company organization chart(s) including a narrative to fully describe all organizational levels, plans and activities. This section must provide a chart of the program organization to be used in performance of the contract including a narrative describing how the Contractor will integrate the management of all elements of the project. This section must identify key technical and management personnel who will be assigned to the project. If the project includes major subcontractors, provide organizational information about for each subcontractor and include subcontractor organizational elements in the project organizational chart. This section must also describe the visibility upper management will have and what oversight will be provided.

B. Roles, Responsibilities, and Relationships. This section must discuss the authority of all responsible management positions identified by the organizational description. The description must include the role of the project manager to direct, control, and commit resources to successfully manage the performance of the contract. This section must describe working relationships the Contractor will establish with the FAA.

C. Policies and Procedures. This section must describe the Contractor’s policies and processes to be used in managing this contract.

D. Communication. This section must describe the communication channels and methods used both internally and externally.

E. Subcontract Management. This section must describe the Contractor’s approach to managing subcontractor activities. Include in the approach the organizational relationship maintained between the prime contractor and the subcontractors and the methods of requirement flow-down and activity progress back to the prime Contractor. This section must describe subcontractor and supplier rating systems used to select subcontractors or vendors and describe the approach to maintaining quality from the products produced by the subcontractors or vendors.

F. Schedule. This section must provide an integrated master schedule (IMS) for the program. The IMS must include all formal reviews and audits, all key programmatic and technical events, and the submission of all documentation identified in the Contract Data Requirements List (CDRL). All developmental and production processes must also be included in the schedule.

G. Schedule Management. This section must describe the Contractor’s approach for monitoring and control of an IMS to include techniques, methods, processes, and procedures. This section must discuss how subcontractor schedules will be integrated and updated, if applicable. This section must discuss the processes and procedures the Contractor will use to track and report progress on this contract.

H. Resource Planning. This section must describe the Contractor’s approach to resource management. This section must discuss the approach to hiring, training, and maintaining quality resources to satisfy the requirements under this contract. This section must discuss the approach to staff the program consistent with the implementation approach and schedule.

I. Performance Management. This section must describe the organization, resources, policies, processes, methods, systems and tools for:

a. Collecting and validating data

b. Monitoring and tracking performance

c. Analyzing performance

d. Reporting and communicating performance

e. Identifying, developing, and implementing preventive, corrective, and remedial actions

J. Data Management. This section must describe the organization, procedures, and tools to be used to ensure that all data deliverables required by the contract are delivered in accordance with the delivery instructions. This section must identify the Contractor’s processes for integrating and maintaining the total data management effort. This effort must include the monitoring, reporting, status accounting, and cross matrixing (e.g., Government change requirements versus implemented changes) of all changes to, additions of, or deletions of CDRL contents. The Contractor’s procedures for controlling generation, receipt, approval, storage, and delivery of subcontractor data as well as its inclusion in status accounting must also be described.

K. Quality Management. This section must describe the Contractor’s specific implementation of the quality management system needed to comply with FAA contract requirements. This section must describe quality objectives, procedures, and processes consistent with the requirements of ISO-9001. This section must discuss documented methods and procedures to ensure quality control of design and development activities, purchasing, test and evaluation, implementation, handling, storage, packaging, and shipping.

This section provides a basis for FAA assessment of the quality system and evidence of the contractor’s intent to comply with the contract quality requirements of this contract.

L. Security. This section must describe the Contractor’s approach to implementation of security provisions, including security authorization and certification activities, personnel and physical security.

M. Metrics. This section must describe the management indicators (i.e., metrics) that will be used to track contract performance and work tasks throughout the contract life cycle. This section must also describe the contract metrics that will be used to monitor the cost and schedule progress for all contract line item numbers (CLIN) under this contract.

N. Risk Management. This section must describe the Contractor’s approach and method for the identification, assessment and mitigation of program cost, schedule and performance risks. The description must include, but is not limited to, the following:

a. identifying risk areas,

b. assessing risk factors,

c. assigning appropriate resources to reduce or eliminate risk factors,

d. identifying and analyzing alternative actions available,

e. identifying the most promising alternatives,

f. and planning for implementation of the risk reduction.

11. Distribution Statement

Monthly Program Status Report, A002

DI-FAA-TSS-PM-002

The Monthly Program Status Report provides the Contractor’s assessment of overall contractual progress, risk identification and mitigation strategies, progress against schedule baseline and identification of variances, performance data, metrics and cost reporting. The report covers achievements, areas of difficulty and provides the Contractor’s approach for correcting and maintaining baseline plans.

4. Approval Date (YYYY/MM/DD)

5. Office of Primary Responsibility (OPR)

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the Tower Simulation System (TSS) contract.

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The Monthly Program Status Report must cover the Contractor and Subcontractor(s) activities if Subcontractors are involved in the TSS contract. The Monthly

Program Status Report must include, but is not limited to, the following:

A. Executive Summary. This section describes the overall status and must contain a narrative summary of contractor and subcontractor (if applicable) performance in meeting the cost, schedule and technical baselines, including significant problem areas, corrective actions taken, and any required Government actions.

B. Accomplishments. This section describes the accomplishments during the reporting period, including the current status of major events and milestones. The report must compare the status of the current month with the prior month’s projections. The report must discuss any problems associated with each milestone and their resolutions. The report will include a 30-day outlook on projected accomplishments.

C. Issues and Concerns. Each issue or concern must be identified and discussed separately. For each issue or concern identified, the Contractor must provide a description of the issue or concern, an assessment of the criticality and time sensitivity of the issue or concern, and actions planned to overcome them. For each action plan proposed, the report must indicate involvement by the Government or subcontractors.

D. Status. The Contractor must provide a narrative summary of the technical, cost, and schedule status and their relationships.

1. Technical. This section must include a discussion of technical performance in each area of the contract for efforts scheduled during the period or in progress during the period. This section must summarize engineering activities performed during the period, to include, status of site activities in relation to planned milestones, status of open Problem Trouble Reports (PTR), Engineering Change

Proposals (ECP), or configuration changes affecting the program during the period.

2. Cost. For any cost-based contract line item numbers (CLIN), this section must address significant cost variances, the cause(s) of the cost variance, the impact on the total contract costs and corrective actions taken. This section must also include a high level cost summary, expenditures for the reporting period, burn rate and percent of work completed for each task order or CLIN.

3. Schedule. This section must status the TSS key milestones identified in the TSS contract. A discussion on schedule delays/variances, the cause(s) for the variance, the impact on the total contract schedule and corrective actions must be addressed. This section must also include the

Contractor’s 3-month outlook on scheduled activities/milestones.

4. Metrics/Performance Data. This section must include a discussion of each metric used for monitoring contract performance.

5. Risk. This section must discuss all medium and high program risks to the technical, cost, or schedule during this reporting period. Each risk must be identified and discussed separately. For each risk identified, the report will provide a description, an assessment of the criticality and time sensitivity, and mitigation plans. Risk analysis must conform to the Risk Management Plans of the

Contractor and the Government. All risks must be statused and tracked until closure by the

Government.

6. Staffing. The Contractor must identify staffing changes affecting key personnel that occurred during the reporting period or planned in the next reporting period.

7. Action Items. This section must include the status of action items resulting from all meetings held during this reporting period. The status must indicate actions as “opened” or “closed”. If opened, the status must indicate the actions taken to close the item. Actions remaining open between the reporting periods must be reported.

Contractor Support Transition Plan, A003

DI-FAA-TSS-PM-003

The Contractor Support Transition Plan (CSTP) describes the methodology for the orderly transfer of system support activities from the current Tower Simulation System (TSS) contract to a new contract.

FAA / AJI - 2230

6a. DTC Applicable

6b. GIDEP Applicable

This Data Item Description (DID) contains the format and content preparation instructions for the Contractor’s

Support Transition Plan as described in Section 3.6 of the Tower Simulation System (TSS) Statement of Work

(SOW).

8. Approval Limitation

9a. References

N/A 9b. AMSC Number

FORMAT AND CONTENT: Contractor format is acceptable. The CSTP must detail the activities that must be undertaken to ensure a smooth transition and assume full responsibility for TSS operation, maintenance, and technical support as described from the current Federal Aviation Administration (FAA) TSS contract to a new contract.

The CSTP must delineate and recommend the time required to ensure a smooth transition with minimal interruption/impact to ongoing and scheduled operational training needs of the FAA air traffic control tower community.

The CSTP must fully explain how the activities delineated in Section 3.2 of the TSS SOW will be addressed to ensure a seamless transition to include, but not be limited to:

a. Plans and processes to be employed to ensure familiarity and the ability required to support the existing and deployed TSS systems/equipment for:

air traffic controller training operational scenario development development, implementation, integration, and maintenance of hardware, unique application or third party software, training materials, visual data bases, models, liveries, etc.

technical support, and repair services

b. Activities, procedures, and schedules for any necessary refurbishment, calibration, checkout, and acceptance of GFE/GFP (e.g., hardware equipment/manuals, site spares, accounting records, as-built drawings, etc.) located at each TSS facility

c. The detailed plan for shipment, installation, and checkout of any GFE/GFP to be transitioned from the current Training System Support Center (TSSC) and the data-sharing repository that is currently accessible over the Web-based Integrated Data Environment (WIDE)

d. Method or procedure of assuming management of any existing TSS related vendor/OEM repair contracts

e. Any recommendations for additional equipment, processes, and documentation which would be beneficial to a successful transition

f. Packaging, preservation, shipping, storage, handling, and marking as required

g. Hardware/software development/testbed system and related documentation

h. Implementation of any technology upgrades, and

i. Any other information necessary for a seamless transition.

Meeting Agenda, A004

DI-FAA-TSS-PM-004

The meeting agenda provides information concerning the purpose, location and schedule of all Tower Simulation

System (TSS) conferences and formal meetings to be conducted under this contract with Government personnel.

4. Approval Date (YYYY/MM/DD)

N/A

5. Office of Primary Responsibility (OPR)

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

N/A

7. Application/Interrelationship

This DID provides the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

9a. References

N/A 9b. AMSC Number

Format and Content: Contractor format is acceptable. The Conference Agenda must include the following information as a minimum, when applicable:

A. The purpose and objective of the conference.

B. Location, date and duration of the conference.

C. A daily chronological listing of each major topic or subtopic to be discussed and time to be devoted to each topic. The presenter or lead for each topic must also be provided.

D. A list of activities to be represented and identification of their responsibilities.

E. A list of subcommittees to be established during the conference and the proposed activity representation for each subcommittee.

F. Reference to a brief description of the results of previous meetings, when relevant.

G. Location, schedule and purpose or subject area to be covered by each subcommittee, when applicable.

H. Names of conference chairperson, co-chair, and subcommittee chairs, when applicable.

I. Information on transportation and administrative service available to conference attendees.

J. Other pertinent information such as forms to be used, identification of any deviations or waivers, security classification and clearance requirements.

Meeting Minutes, A005

DI-FAA-TSS-PM-005

The Conference Minutes are prepared by the Contractor to document the significant event, results, and action items of the formal reviews, conferences, meetings, and audits conducted under this Tower Simulation System

(TSS) contract.

4. Approval Date (YYYY/MM/DD)

N/A

5. Office of Primary Responsibility (OPR)

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

N/A

7. Application/Interrelationship

This data item description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the TSS contract.

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

Format and Content. Contractor format is acceptable. The Conference Minutes should contain, but are not limited to, the following:

A. Title Page – The title page to contain the following:

a. Title – Name of conference or meeting.

b. Contract Number.

c. System Name – Tower Simulation System (TSS)

d. Date(s) of conference or meeting.

B. Introduction – Statement or summary explaining the purpose and/or objective of the meeting.

C. Administrative Data – Location of meeting and a list of all meeting attendees (e.g., name, company or agency, job title, routing symbol, telephone number and email address).

D. Material Reviewed – A description and/or listing of all topics, documentation and other material discussed during the meeting.

E. Meeting Decisions – A complete and accurate description of all decisions made at the meeting.

F. Revisions Required – If applicable, the specific statements relating to all changes and/or additions required to the documents reviewed and the reasons for the revision.

G. Baseline Changes – If applicable, a description of all changes to the established baselines required as a result of the meeting. This must include for each change required: description of the change, the justification for the change, and identification of the organization(s) responsible for preparing the change package necessary to affect the change.

H. Action Items or Outstanding Problem Areas – Statements relating to any problem areas that could not be resolved during the meeting. Include for each action or problem:

a. Statement of the problem.

b. Identification of all organizations and people designated to resolve each problem.

c. Date by which the contractor is to submit a resolution to the procuring agency for approval.

d. Action to be taken by the contractor pending resolution of the problem.

e. Closure procedure.

I. Meeting Agenda. A copy of the approved agenda, revised to reflect actual meeting conduct.

Configuration Management (CM) Plan, A007

DI-FAA-TSS-CM-001

The Configuration Management (CM) Plan describes the organizational structure of the Contractor’s configuration management organization; the Contractor’s procedures for identifying and documenting the functional and physical characteristics of hardware and software configuration items; controlling changes to those characteristics; and recording and reporting change processing implementation status.

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the Tower Simulation System (TSS) contract.

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The CM Plan must be prepared in accordance with the applicable sections of FAA-STD-021 for Commercial Off The Shelf (COTS) equipment.

Request For Deviation/Waiver, A008

DI-FAA-TSS-CM-002

A Request for Deviation must be submitted to the Government to request authority before the fact to temporarily deviate from the mandatory requirements of the Tower Simulation System (TSS) specification requirements.

A Request for Waiver must be submitted to the Government to request a Government waiver permitting the

Contractor to deliver a manufactured item to the Government that does not conform to the TSS specification requirements.

A Request for Deviation or a Request for Waiver enables the Government to determine the impact on cost, schedule, performance, operation, logistics support or other affected TSS Program areas.

4. Approval Date (YYYY/MM/DD)

N/A

5. Office of Primary Responsibility (OPR)

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. Each Request for Deviation and Request for

Waiver must be prepared in accordance with FAA-STD-021 and include the following information at a minimum:

A. Request Summary. Include background information and an explanation of why the request is being made.

B. Reference documents. This section must contain reference to all applicable documents, including the approval dates and the date of any applicable amendments, notices, and revisions, as specified in the TSS contract.

C. Content. The request must include the consideration to be provided to the Government if the Government accepts the request, and, where applicable, the following information:

1. A complete description of the contract requirement affected and the nature of the deviation (i.e., non-conformance).

2. Number of units or items (and serial/lot numbers) to be delivered in this configuration.

3. Any impact to the operational use of the TSS systems or units resulting from the non-conformance.

4. Any impacts to logistics support elements (such as software, manuals, spares, tools and training) being utilized by Government personnel or to the operational use of the product.

5. Information about remedial actions being taken to prevent reoccurrence of the non-conformance.

Specification Change Notice, A009

DI-FAA-TSS-CM-003

A Specification Change Notice (SCN) is used to record and transmit approved change pages to the existing

Tower Simulation System (TSS) specification. After an Engineering Change Proposal (ECP) has been approved by the Government, the SCN provides official notice to holders of the TSS specification that the attached change pages can be incorporated into their copy of the TSS specification.

5. Office of Primary Responsibility (OPR)

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The SCN must include the following information at a minimum:

A. Reference Documents. The applicable issue of any documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, must be as specified in the contract.

B. Content. The SCN content must include, where applicable, the following information:

1. A listing of the identifier, revision level, and title of the affected specification.

2. The identifier of the ECP which proposed the change of this SCN.

3. A summary of all previously approved SCNs against this revision of the specification and the page numbers affected by those previous SCNs.

4. Attached copies of the change page(s) to be incorporated into the specification if the SCN is approved by the Government.

Engineering Change Proposal (ECP), A010

DI-FAA-TSS-CM-004

An Engineering Change Proposal (ECP) provides the documentation in which the proposed engineering change is described. It must include change impacts to the Tower Simulation System (TSS) system, configuration items, and other associated configuration documentation affected by the proposed change. In addition, it must describe how the proposed change will be implemented along with providing estimated schedules and associated costs.

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The ECP must include, where applicable, the following information as a minimum:

A. Change priority, change classification, and change justification.

B. Complete description of the change to be made and the need for the change.

C. Complete listing of all configuration items (CI) impacted by the proposed change and a description of the impact on those CI’s.

D. Proposed changes to documents controlled by the Government.

E. Proposed serial (or lot) number effectivities of units to be produced in, or retrofitted to, the proposed configuration.

F. Recommendation about the way a retrofit should be accomplished.

G. Impacts to any logistics support elements (e.g., software, manuals, training, spares, etc.) being utilized in support of the TSS.

H. Impacts to the operational use of the TSS.

I. Complete estimated life-cycle cost impact of the proposed change.

J. Milestones relating to the processing and implementation of the ECP.

Contract Change Proposal, A011

DI-FAA-TSS-CM-005

A contract change proposal (CCP) is used to propose, control, and approve “non-baseline” changes to the Tower

Simulation System (TSS) contract. A CCP cannot be used for making changes to contract specifications, clauses or other baseline documentation. In the event changes to both baseline and non-baseline documents are necessary; all changes should be submitted to the Government using an Engineering Change Proposal (ECP).

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The CCP must include, where applicable, the

A. Control number and date of preparation. A unique number must be assigned to each CCP. The date of preparation must also be included.

B. Title. A descriptive title must be assigned.

C. Items affected. Identify the area(s) of the contract which are affected by the proposed changes (e.g., contract data requirements list, statement of work paragraph, plan, or contract section).

D. Statement of justification and alternatives. Provide reason for the change and present viable alternatives which may exist. Include impact statement to address impact of not making the change.

E. Description of proposed change. Provide a detailed description of the proposed change.

F. Schedule. Provide working schedule for implementation of the CCP, including target date for implementation via contract modification. If conditions exist which make implementation urgent, a brief explanation should be included.

G. Estimated cost. Provide a not-to-exceed (NTE) estimated cost (or estimated savings) expected as a result of implementing the change.

Integrated Logistics Support Plan (ILSP), A012

DI-FAA-TSS-ILS-001

The Integrated Logistics Support Plan (ILSP) delineates the hardware/software maintenance concept and life cycle support strategies/activities for the current and future Tower Simulation Systems (TSS).

4. Approval Date (YYYY/MM/DD) 5. Office of Primary Responsibility (OPR)

6b. GIDEP Applicable

This Data Item Description (DID) contains the format and content preparation instructions for the Integrated

Logistics Support Plan that addresses the requirements specified in Sections 3.1.1.4, 3.1.1.5, 3.1.1.6, 3.1.1.7, 3.1.1.8, 3.1.1.9, Section 3.1.2 (including the subsequent sub-sections), Section 3.1.3 (including the subsequent sub-sections), Sections 3.1.4, 3.1.5, 3.1.6, and Section 3.2 (including the subsequent sub-sections) of the TSS

Statement of Work (SOW).

9a. References

N/A 9b. AMSC Number

FORMAT AND CONTENT: Contractor format is acceptable. The Integrated Logistics Support Plan (ILSP) is the source document describing the implementation of the Contractor's approach for life cycle logistics support of the TSS. Since the majority of TSS is Commercial-Off-the-Shelf (COTS) and is intended to be Contractor maintained and supported for all TSS deployed now and in the future, the ILSP must document their approach to providing an integrated logistics support process; establish a national logistics support plan for the TSS; ensure the interoperability and operational availability of all TSS system/subsystem components and functions throughout its life cycle; and effectively manage system upgrades to ensure continued system effectiveness and supportability. The ILSP must be organized into the sections as described below:

Section 1 – Introduction

The Contractor must provide a concise statement on the scope of the ILSP and how they will manage and execute their responsibilities in the creation of the TSS integrated logistics support program.

Section 2 – System Characteristics

The Contractor must provide a brief summary of the TSS system/subsystem components and identify those components worthy of logistics supportability concerns, if any.

Section 3 – Logistics Tasks

The Contractor must provide a description of how they intend to accomplish the following tasks:

a. implement hardware configuration management, maintenance/repair, and support on-site at each TSS facility with support as needed from their Training System Support Center (TSSC)

b. implement software configuration management, maintenance/repair, and support on-site at each TSS facility with support as needed from their TSSC

c. support the development/delivery of TSS training, training documentation/evolutions to include the generation and maintenance of TSS visual databases (VDBs), models, liveries, and scenario development

(tools and resources)

d. support the development/use of a TSS web-based interactive data repository that addresses the requirements as specified in Section 3.1.2.2.10 of the TSS Statement of Work (SOW)

e. ensure system operational availability of 95% at each TSS facility as specified in Section 3.1.1.4 of the

TSS Statement of Work (SOW)

Obsolete Parts List, A013

DI-FAA-TSS-ILS-002

The Obsolete Parts List delineates the set of obsolete or obsolete in the near future, parts of the Tower Simulation

System (TSS).

6b. GIDEP Applicable

This Data Item Description (DID) contains the format and content preparation instructions for the Obsolete Parts

List as specified in Sections 3.1.1.7 and 3.1.1.8 of the TSS Statement of Work (SOW).

9a. References

N/A 9b. AMSC Number

FORMAT AND CONTENT: Contractor format is acceptable. The generation and update of the Obsolete Parts

List must be an ongoing activity during the contract period of performance. It must be a result of the Contractor’s subscription to vendor product service bulletins to obtain notices on product availability, specifically as it applies to future obsolescence of parts used within the TSS. The list must identify the item name, manufacturer, part number, National Stock Number (NSN), if applicable, and the date in which it will no longer be available for purchase. The list must also include the item name, manufacturer, part number, National Stock Number (NSN), if applicable, and the unit price and date of availability for the recommended/suggested replacement part.

Recommended Site Spares List, A014

DI-FAA-TSS-ILS-003

The Recommended Site Spares List delineates the requisite set of on-site spares necessary to support the operational availability of each installed Tower Simulation System (TSS).

4. Approval Date (YYYY/MM/DD) N/A

6b. GIDEP Applicable

This Data Item Description (DID) contains the format and content preparation instructions for the Recommended

Site Spares List to ensure the TSS meets the operational availability requirements specified in Section 3.1.1.4 and is managed as delineated in Sections 3.1.1.5 and 3.1.1.6 of the TSS Statement of Work (SOW).

9a. References

N/A 9b. AMSC Number

FORMAT AND CONTENT: Contractor format is acceptable. The Contractor must provide a complete parts list, identifying the quantities of each part at each TSS site. The list must designate parts as Exchange and Repair

(E&R), “expendable” or “consumable”. The list must be arranged in a top down breakdown sequence by major assembly. Under each major assembly, the Contractor must list the E&R parts, expendables or consumables used in repair of the assembly. The list must include the item name, manufacturer, part number, National Stock

Number (NSN), if applicable, and unit price for each part.

Site Survey Plan, A015

DI-FAA-TSS-ENG-001

The Site Survey Plan must describe the tasks required to prepare Federal Aviation Administration (FAA) facilities for the installation/implementation of the Tower Simulation System (TSS), including analysis of the key areas of risk entailed in the installation/implementation activities and the Contractor’s specific approach to minimize impact on the site facility, mission and personnel.

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The Site Survey Plan must describe the

Contractor’s approach for conducting site surveys for TSS installation in FAA facilities. The Site Survey Report must define the scope and content of the resulting site survey products to specifically include the items required by the Site Survey Report.

Site Notification Letter, A016

DI-FAA-TSS-ENG-002

A Site Notification Letter provides the information necessary to request permission for the Contractor to conduct a site survey at a Federal Aviation Administration (FAA) facility in order to install the Tower Simulation System

(TSS) at the facility.

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The following information mustshall be included in the Site Notification Letter as a minimum:

A. Brief statement explaining the purpose of the visit. Include a reference to the FAA TSS contract and the name, email address, and telephone number of the FAA TSS Program Manager in this section.

B. Preferred date(s) and an alternative date(s).

C. Expected duration of visit.

D. Information and data to be obtained during the visit.

E. Any days or periods of time that the site survey cannot be conducted (e.g., night, when airport is closed, etc.).

F. Any special access that is required at the FAA facility.

G. Any facility or TSS related information that can be prepared or collected by the FAA facility prior to the

Contractor Site Survey visit.

H. List of all Contractor equipment (e.g., computers, cameras, etc.) that will be used at the FAA facility.

I. Names and job titles of all Contractor personnel that will be visiting. If names cannot be provided provide the number and type of Contractor personnel that will be visiting. Security information should also be provided for each Contractor personnel.

Facility Design Criteria, A017

DI-FAA-TSS-ENG-003

The Facility Design Criteria (FDC) identifies the specific technical requirements upon which the facility design is to be predicated before the detailed design is started. The criteria are qualitative in nature and can be translated into detailed installation plans for the Tower Simulation System (TSS) required by this contract.

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The FDC document must include the following information as a minimum:

A. Scope.

1. The FDC document is to describe the facility requirements for the system. The FDC will not mandate specific construction methods or materials, but it must establish performance requirements. It should not address the problem of total workload on a particular common-use facility generated by a mixed force of similar systems, nor should it assume anything about the quantity and types of facilities available at a particular development site.

2. This section of the FDC document must begin as follows: “This part of the document establishes the requirements and basic restraints or constraints imposed upon the development of an architectural and engineering (A&E) design for the Federal Aviation Administration (FAA) facility in support of the

Tower Simulation System (TSS).” Subsequent sentences and paragraphs must briefly describe the intended purpose and general use of the facility with respect to the system to which it is related.

B. General concept. Describe the use to which the facility will be put. Describe the flow of personnel, material, and maintenance. Describe the functions to be performed in the facility, including time elements, number of pieced for an eight-hour day as an example.

C. Siting and layout.

1. Include an area layout showing location of the facility with respect to general area.

2. Include a detailed site layout to provide site selection information and constraints such as those listed in the subparagraphs below, if applicable, for guidance to using service facility planners who will perform the site selection and layout at the bases scheduled to receive the new system.

a) Access requirements; special width requirements.

b) Required relationships between outside elements.

c) Clearances.

d) Parking, loading, required setbacks, paving, any other related requirements.

e) Explosive hazards data.

3. Provide a floor layout of the required facility to show:

a) Functional arrangement of areas.

b) Dimensional requirements.

c) Height requirements (cross sections or elevations as required).

d) Location of real property installed equipment.

e) Doors; heights, widths, and location of entrances.

f) Clear-span requirements (no column intrusion allowed).

g) Location of special electrical or mechanical provisions.

h) Special foundations required.

i) Blackouts, elevations, anchor bolts, or provisions for “not in contract” equipment.

j) Hoist requirements (locations and loads).

4. General criteria.

a) Architectural (if applicable)

1. Personnel occupancy types; hours per day.

2. Designation of use of areas within the facility.

3. Types of special and oversized doors required.

4. Floor level requirements. Floor drainage.

5. Controlling or critical dimension requirements.

6. Window requirements (if any).

7. Security requirements (vaults, secure storage rooms, secure conference rooms or related structures).

b) Structural (if applicable)

1. Crane and hoist locations and loads. Control requirements.

2. Floor loads (pounds per square foot).

3. Point or concentrated loads (pounds and dimensions).

4. Clear span and column free area(s).

5. Blast loads; shielding requirements.

6. Personnel ladders; elevators (freight load requirements)

7. Transfer piers; dock loads.

8. Clear ceiling heights.

c) Mechanical (if applicable)

1. Interior potable water (state if unusual quantities or qualities are required).

2. Environmental limits. Temperature, humidity, and ventilation.

3. Compressed air.

4. Fire protection.

5. Vibration and acoustical requirements.

6. Equipment cooling requirements (British Thermal Units (BTU) per hour)/

7. Special mechanical systems (hydraulic, cooling, or other special requirements).

d) Electrical

1. Power requirements – type and magnitude (voltages, frequency, phase, quality, and allowable tolerances.)

2. Light intensities

3. Communications requirements.

4. Grounding (type and location).

5. Power factor.

6. Backup power requirements.

e) Equipment. Provide layout and list each piece of equipment.

1. Equipment designation.

2. Number of units required.

3. Purpose of equipment.

4. Size of equipment (governing dimension and weight).

5. Power requirements (alternating Current (AC) volts, phase, frequency, Direct

Current (DC) volts, normal and peak kilowatts (KW), and power factor(s).

6. Cooling requirements – heat gain (BTU’s per hour), type cooking, in-out temperatures, and relative humidity requirements.

7. Minimum access requirements, front, back, and sides.

8. Other system requirements (hydraulic, compressed air, or other special requirements).

f) Special Features – special requirements not covered above.

g) Operability and maintainability requirements.

h) Hazards and effects.

1. Radio Frequency (RF) radiation.

2. X-ray radiation.

3. Lightning

4. Other hazards (smoke, explosion, and any other)

i) System expansion potential.

j) Safety.

Site Survey In-Brief, A018

DI-FAA-TSS-ENG-004

The Site Survey In-Brief provides information related to the implementation of the Tower Simulation System

(TSS) at a Federal Aviation Administration (FAA) facility. The Site Survey In-Brief must be held with personnel from the FAA facility at the start of each Site Survey.

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The following information must be provided during each Site Survey In-Brief as a minimum:

A. Overview of the TSS Program.

B. Introduce each member of the Contractor TSS team by name and job title. Provide a telephone number for the Contractor Team Lead for contact purposes.

C. Explain the purpose of the site visit.

D. Expected duration of visit.

E. Information and data to be obtained during the visit.

1. To be obtained by the Contractor

2. To be provided by the FAA facility

F. Discussion involving facility and/or airport access, hours of operation, Contractor equipment to be used to collect information during the site visit, etc.

G. Proposed schedule for the implementation of the TSS to include pre-installation work, installation and checkout of the TSS, site adaptation, and training.

Site Survey Report, A019

DI-FAA-TSS-ENG-005

The Site Survey Report provides the results of the site survey and the tasks necessary to implement the Tower

Simulation System (TSS) at a Federal Aviation Administration (FAA) facility.

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The Site Survey Report must include the content in the approved Site Survey Plan. The plan must include the following as a minimum:

A. Site Survey results.

B. Site Preparation Requirements. The report must address all site preparation tasks required to install the

TSS. Include specific conditions, facilities, issues, and other concerns that may adversely affect the ability of the Contractor to perform the installation of the TSS. The report must identify those concerns that are the responsibility of the Government to correct, beyond the capability of the Contractor, or those considered to be beyond the scope of the TSS contract. The Contractor should make recommendations for solutions to the areas of concern.

C. Equipment Installation. The report should address all tasks necessary to install the TSS, including ancillary equipment.

D. Site Test and Implementation Activities.

E. Schedule. A complete integrated schedule must be provided for the pre-installation, installation, and verification of the TSS at the FAA facility.

Site Installation Drawings, A020

DI-FAA-TSS-ENG-006

The Site Installation Drawings document the physical installation of the Tower Simulation System (TSS) at a

Federal Aviation Administration (FAA) facility.

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

This data item description (DID) contains the format and content preparation instructions for the data product

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The Site Installation Drawings must include the

A. Floor and Equipment Layout. The drawings must show the location of all installed TSS and non-TSS equipment, units, systems, components, and items in each room or compartment that contains TSS equipment or components. The size and location of each item installed in the spaces where the TSS equipment is installed must be presented in horizontal and vertical distances from the floor and walls. The drawings must include the name, size, purpose, and location of each TSS component. The floor layout must address the following installation information as a minimum:

Functional arrangement of areas

Dimensional requirements

Height requirements

Location of all TSS and non-TSS equipment in the spaces

Doors – height, width, and location of entrances

Location of special electrical or mechanical provisions

Special foundations required

B. Power Requirements. All power requirements and power connections for all TSS equipment must be provided in the drawings. The type and magnitude (i.e., voltage, frequency, phase, quality, and allowable tolerances) must be provided for each TSS components. Any backup power requirements must also be provided.

C. Cooling Requirements. The total amount of heat generated by the TSS equipment in each area or space must be provided in British Thermal Units (BTU) per hour.

D. System Connections. All internal and external connections must be provided for all TSS components. All cables should be labeled in the drawings.

E. Maintenance Access. All access dimensions required for performing maintenance or replacement of each

TSS component must be provided in the drawings.

F. Safety Requirements. All safety requirements necessary for the TSS installation must be provided in the site installation drawings.

G. Site Preparation Requirements. The report must address all site preparation tasks required to install the

TSS in the designated spaces. Include specific conditions, facilities, issues, and other installation related information.

Test Plan, A021 & A026

DI-FAA-TSS-TEST-001

The Contractor’s Test Plan defines the overall test philosophy, test definitions, and summarizes all tests to be conducted during the Tower Simulation System (TSS) testing. It also describes methods for implementing and controlling the Contractor’s TSS test program.

FAA / AJI-2230

6a. DTC Applicable

N/A 6b. GIDEP Applicable

N/A

7. Application/Interrelationship

This data item description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the TSS contract.

8. Approval Limitation

N/A 9a. References

N/A 9b. AMSC Number

FORMAT and CONTENT. Contractor format is acceptable. The Contractor’s Test Plan must include, but is not limited to, the following sections:

A. Introduction. This section must provide an overview of the Contractor’s TSS test program. The

Contractor must provide a general description of the tests to be conducted, location of where the test(s) will be conducted, and a systematic…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .