Amendment 0003 Section J-5 CDRLs and DIDs.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

DATA ITEM DESCRIPTION

1. TITLE

Equipment/Systems Modification

2. IDENTIFICATION NUMBER

DID-CM-001

3. DESCRIPTION/PURPOSE

3.1 The purpose of this report is to provide an instrument for the Government to track implementation of an Engineering Change Proposal/Material Change/ Modification Work Order (ECP/MC/MWO).

This report will permit the Government to track contractor’s modification of government equipment.

4. APPROVAL DATE

03/31/2017

5. RESPONSIBLE OFFICE

Facility Security Risk Management

(FSRM)

6. REFERENCE

FAA AMS

7. APPLICATION/INTERRELATIONSHIP

7.1 This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract.

8. PREPARATION INSTRUCTIONS

8.1 Format. Document must be prepared on 8.5 x 11 inch paper. The deliverable must be presented in electronic 2010 MS Office Standard file.

8.2 Cover Sheet. Each report must have a cover sheet with identifying nomenclature and title centered on the sheet along with the ECP and MC or MWO titles and numbers. In addition, identify the center Major Assembly affected.

Each page of the report must be page numbered in the upper right hand corner.

Each page of the report must contain the ECP number and the MC or MWO number in the upper right hand corner.

The first page of the report must contain the month, day and year for the report and on a second line the estimated completion date of the ECP and the MC or MWO.

8.3 Additional Format and Content Instructions.

Purpose of the Modification. Describe what capability is added, deleted, changed or what deficiency is corrected.

Problem Areas Encountered. Describe any problem areas encountered during the application of the modification and any additional required actions.

Tabulation of Retrofit Actions. List all sites making the modification along with the following data in tabular format for each site.

a. Site Identification.

b. Serial Number of Items Modified.

c. Number of Items to be Modified.

d. Number of Items Modified This Period.

e. Number of Items Remaining Unmodified.

Total Tabulation. Total all the items to be modified under this ECP/MC/MWO, total all items modified this period, and total all items remaining to be modified.

AS-BUILT MATERIALS LIST - BILL OF MATERIAL (BOM) LIST

DID-CM-002

3.1 This list details the equipment used to repair obsolete equipment, systems, or subsystems at each site when new equipment is required after the failure of obsolete equipment that cannot be repaired.

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

8.1 Format. The list must be in the Contractor’s format. The deliverable must be presented in electronic format 2010 MS Office Standard file.

8.2 Content. The List must contain the following information for any systems, subsystems or major components delivered to the government, including those that are repaired and modified.

a. Part name

b. Part number and revision

c. Serial number

d. Manufacture date

e. Manufacturer

f. Next higher assembly part number and serial number

g. Unit Price

h. Indenture level

i. Engineering change proposals

j. Waivers

k. Deviations

l. Software part number and revision as applicable for each serial number controlled or lot number controlled all-up round

m. Section, assembly, subassembly, part or component installed in the end item at time of delivery to the government.

n. Lowest Replaceable Unit (LRU) at Organizational/Field Level Maintenance.

MODIFICATIONS TO AS-BUILT FACILITY DRAWINGS

DID-CM-003

3.1 A modification to As-built facility drawings describes the red-line changes to a facility security drawings and applicable configuration documents during repair actions by the contractor.

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

8.1 Format. The list must be in the Contractor’s format.

8.2 Content. Security Drawings - Technicians conducting repair actions will redline existing facility drawings to indicate changes to equipment and/or configuration of existing systems

COST PERFORMANCE REPORT

DID-FD-001

3.1 This report is used by the Government to track the final cost for each of the Unique Work Order Numbers by facility type in relation to travel, equipment, and work hours to complete repair.

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

8.1 Format. Contractor format is encouraged. The deliverable must be presented in electronic 2010 MS Office Standard file.

8.2 Content.

Each Unique Work Order Number should be searchable for costs for Travel, Labor, Parts, and Logistics Support (Shipping, storage, handling, etc). The CPR must contain the following:

1. Travel Costs by Facility Type

a. ARTCC

b. TRACON (Tier One)

c. ATCT (Tier One)

d. ATCT (Non-Tier One)

e. ARSR

f. Facilities not contained in a-e.

2. Equipment Costs by Facility Type

i. Surveillance (including ECV and GCV)

ii. Access Control

iii. Intrusion Detection

iv. Perimeter Intrusion Detection

v. Gates

vi. Barrier Arms

b. TRACON (Tier One)

c. ATCT (Tier One)

ii. Access Controls

d. ATCT (Non-Tier One)

i. Access Controls

ii. Entry Control Video (ECV)

iii. Gate Control Video (GCV)

iv. Gate Operator

v. Barrier Arms

3. Labor Costs, including hours per repair by Facility Type

b. TRACON (Tier One)

c. ATCT (Tier One)

d. ATCT (Non-Tier One)

4. Total Cost by Unique Work Order Number (Contractor should provide listing of the Unique

Work Order Numbers by facility type and organized by facility IDs). Cost data should be isolated by:

b. TRACON

c. ATCT Tier One

d. ATCT Non-Tier One

MAN HOURS

DID-FD-002

3.1 This chart is an index of contractor effort. It is used by the Government to compare the actual man hours expended over the course of each reporting period (Program Management Review). Intent is to address repair hours and the causes for duration of repair actions.

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

8.1 Format. Contractor format is encouraged. The deliverable must be presented in electronic 2010 MS Office Standard file.

8.2 Content.

1. Average Hours per Repair of Failed Card Reader

2. Average Hours per Repair of Failed Control Panels by Panel Type

- CK720

- CK721

- RDR2

3. Average Hours per Repair of Camera by Classification

- Alarm Assessment,

- Visual Identification, and

- Perimeter Area

4. Average Hours per Repair of Head End Video Recording Systems

5. Average Hours per Repair of Perimeter Intrusion Detection Systems

6. Ad Hoc Category

LOGISTICS SUPPORT PLAN

DID-ILS-001

3.1 The Integrated Support Plan (ISP) is provided in two parts and describes the contractor's plans for the management, control, execution, interface, and integration of all aspects of the contractor's logistics support for FSRM corrective maintenance of physical security systems and subsystems at approved staffed facilities

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

8.1 Format. The list must be in the Contractor’s format. The deliverable must be presented in electronic 2010 MS Office Standard file.

8.2 Content. The Logistics Support Plan is the source document describing the implementation of the contractor's approach for logistics support of the FAA FSRM CMC III. It must include the following data:

PART I GENERAL:

SECTION 1 - INTRODUCTION. This section must provide a concise statement on the scope of the logistics support and how the contractor will manage and execute the contractual requirements of the CMC III logistics support program.

SECTION 2 - SYSTEM CHARACTERISTICS. This section must provide a brief summary of the FSRM Security Level 2 through Security Level 4 major components and subsystems, indicating those worthy of logistics supportability consideration.

SECTION 3 - LOGISTICS TASKS. This section must contain a description on how the contractor must accomplish logistics support tasks as identified below:

a. Hardware and Software Maintenance Concept. The Government intends and believes that the FSRM Security System hardware and software can and should be entirely Commercial Off-the-Shelf (COTS). Consequently, the FSRM hardware maintenance concept will be on-site and as-needed. On-site maintenance will include fault detection and removal and replacement of failed line replaceable units (LRU). An LRU is that item to which the CMC III contractor isolates faults for removal and replacement. The contractor must:

1. Discuss the procedures and planned management/control functions to (a) maintain the Security System software and hardware through the initial base year and each of the four option years of the contract.

2. Discuss the Remote Maintenance Monitoring System (RMMS) concept for CMC III. The RMMS must provide a priority scheme so that essential functional capabilities can be retained in the event of subsystem and or equipment failures, and in response to system loading. Describe the maintenance activity data collection processes such as logging, tracking, and scheduling related to the maintenance concept.

3. Discuss the approach to document and satisfy optional periodic, preventative and/or routine maintenance. Specifically address COTS material, warranty, and subscription service implications.

4. If applicable, discuss the impact of modifying COTS items for the FSRM Security Systems application. If the contractor elects to modify COTS, the approach towards documenting the change(s), providing the Government the opportunity to technically and logistically review the resulting impacts, and how the modifications can best be supported for the FSRM Security Systems life cycle must be addressed.

5. If applicable, discuss the impact and logistical supportability planning for any new development software and hardware item. The contractor without specific Government approval, must not develop software or hardware items for use in FSRM Security Systems without the approval of the CO. If the contractor develops software or hardware, the approach towards documenting the change(s), providing the Government the opportunity to technically and logistically review the resulting impacts, and how the modifications can best be supported for the Security Systems life cycle must be addressed.

b. Software Maintenance Concept. FSRM Security Systems software will be maintained by the contractor. All subsequent changes must be approved by the FAA at the lowest manageable software level. The contractor will be formally authorized to make changes to these software module levels, recompile, re-build, and release new versions only upon Government direction. The contractor must describe the procedures for:

1. Ensuring the correct labeling and marking of software identification (discrete part/item identification number) upon physical storage or transfer media.

2. The verification of software run versions on screens, displays, Maintenance Data Terminals or other user devices.

3. The correct labeling, marking, and provisioning of all FSRM Security Systems specific firmware devices, if applicable.

c. LRU Replacement/Repair Approach. The Government’s goal is to initiate a contractor repair service for a period of five years from the date of the first CMC III award. The Contractor must replace failed reparable assets for a period of five years from the date of the CMC III award.

d. Initial Spares. The Contractor must identify initial spares necessary to meet FSRM Security Systems Return-to-Service requirements (SOW). The contractor must describe his methodology for determining the optimum spares set, how the recommendation will be validated through experience, and how spares returned for repair will be repaired to retain operational interchangeability.

e. Test Equipment. The Contractor must describe any peculiar test equipment necessary to support the security equipment and software identified in the J-Attachments. It is not the Governments preference to utilize any peculiar test equipment, so justification must be provided as well as cost, schedule and alternatives.

f. Technical Manuals. The Contractor must utilize Technical Manuals (TMs) provided by the FSRM Program Office from deliverables received from FAA Security System Design and Implementation (SSDI) contracts.

PART II TRAINING: The contractor may recommend training for security specialists and field technicians that would be expected to increase repair efficiency. Areas of training should include:

a. System Software Maintenance Training

b. Hardware Maintenance Training

c. Test Team Training (2nd level maintenance)

d. System Testing Training

CONTRACT DATA REQUIREMENTS LIST

(1 DATA ITEM)

FORM APPROVED OMB NO.

0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY

CLIN X010 TDP TM OTHER ( CONTRACT REQUIREMENT)

D. SYSTEM / ITEM E. CONTRACT / PR NO. F. CONTRACTOR

MEETING RECORDS AND MINUTES TBD TBD

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE OF DATA ITEM

AD-001 MEETING RECORDS AND MINUTES N/A

4. AUTHORITY (DATA ACQUISITION DOCUMENT NO.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

SOW PARA. C.2.0 FACILITY SECURITY RISK MANAGEMENT

7. DD 250 REQUIRED 8. APP CODE 9. DIST STATEMENT REQUIRED 10. FREQUENCY

N/A N/A NO 10 BUSINESS DAYS AFTER

ALL MEETINGS

11. AS OF DATE 12. DATE OF FIRST SUBMISSION 13. DATE OF SUBSEQUENT SUBMISSION

N/A SEE BLOCK 16 SEE BLOCK 16

D I S T R I B U T I O N

B. COPIES B. COPIES

A. ADDRESSEE FINAL A. ADDRESSEE FINAL

DRAFT REG REPRO DRAFT REG REPRO

FSRM COR 1 1

CO 1 1

(A) TOTAL 0 2 2 (B) TOTAL

15. TOTAL OF A & B 4

16. REMARKS:

1. THE CONTRACTOR MUST SUBMIT THE MEETING RECORDS AND MINUTES, NO LATER THAN 10 BUSINESS DAYS AFTER

ALL MEETINGS.

2. THE GOVERNMENT WILL REVIEW AND COMMENT OR APPROVE OF THE MEETING RECORDS AND MINUTES WITHIN 30

BUSINESS DAYS AFTER RECEIPT.

3. THE CONTRACTOR MUST UPDATE AND RESUBMIT THE MEETING RECORDS AND MINUTES, AS REVISIONS OCCUR

WITHIN 10 DAYS FOR APPROVEL.

4. FINAL COPIES: CONTRACTOR IS REQUESTED TO PROVIDE THE GOVERNMENT WITH AN ELECTRONIC COPY.

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

BYRON WILSON

SYSTEMS OFFICE

03/31/17 DAVE JOYCE

03/31/17

Proposed Spares List

DID-ILS-002

3.1 The Proposed Spare Parts List Must contain the contractor’s recommended quantities of every type of spare part required for the system, to include all consumable and expendable items. This list Must explain any assumptions, formulas, or models used by the contractor in the creation of the list.

The Proposed Spare Parts List is used to determine spare parts stocking levels.

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

8.1 Format. The Proposed Spare Parts List format must be arranged in a comprehensive presentation of components, subassemblies, and assemblies as selected by the contractor. The deliverable must be presented in electronic 2010 MS Office Standard file.

8.2 Content. The Proposed Spare Parts List content must include the following:

a. Complete item name

b. Prime manufacturer’s or vendor’s part number

c. Commercial and Government Entity (CAGE) Code

d. National Stock Number (NSN)

e. Quantity per end item

f. Unit of issue (e.g., each, feet, lot)

g. Estimated unit price

h. Recommended quantity to sustain operation for the time period and under the conditions stated in the contract

i. Alpha numeric numbering of items on list

j. Shelf life (if not indefinite)

k. Mean-Time-Between-Failure of each item

l. Production lead time for each item

m. Explanatory narrative, which describes the recommended quantity to take into account multiple end items at a single location

REPORTS TO COR TBD TBD

AD-002 REPORTS TO COR N/A

N/A N/A NO 10 WORKING DAYS AFTER

COMPLETING REPAIR. AND

ALL OTHER REPORTS

WEEKLY/MONTHLY/

QUARTERLY.

FSRM COR ON-GOING

CO ON-GOING

(A) TOTAL 0 0 2 (B) TOTAL

15. TOTAL OF A & B 2

1. ALL RECORDS AND COPIES OF REPORTS MUST BE TURNED OVER TO THE COR WITHIN FIVE CALENDAR DAYS AFTER CONTRACT COMPLETION VIA WEB AND ALL OTHER REPORTS WEEKLY/MONTHLY/QUARTERLY. ALL OTHER REPORTS MUST

BE REPORTED IN A CONSOLIDATED FORMAT.

2. ALL DOCUMENTS MUST BE FILED OR UPDATED WITHIN 10 WORKING DAYS OF THE COMPLETED REPAIR. THE GOVERNMENT

MUST HAVE ACCESS TO THESE FILES UPON REQUEST.

3. THE ENTIRE FILE MUST BE TURNED OVER TO THE GOVERNMENT UPON COMPLETION OF THE CONTRACT.

4. THE GOVERNMENT WILL REVIEW AND COMMENT OR APPROVE OF THE REPORTS AS NEEDED

PARTS MANAGEMENT PLAN

DID-ILS-003

3.1 The plan details the contractor’s parts management program.

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

8.1 Format. The list must be in the Contractor’s format. The deliverable must be presented in electronic 2010 MS Office Standard.

8.2 Content. The plan must detail the contractor’s parts management program. The management program must be in accordance with FAA Order 4600.27C Personal Property Management, AMS asset management process, AMS Clause 3.10.3-2 and all applicable contract clauses.

Parts List The parts list, if required by contract, must contain the following information:

a. Vendor part number with no wildcards.

b. CAGE code of the manufacturer.

PERSONNEL RESUME TBD TBD

AD-003 PERSONNEL RESUME N/A

N/A N/A NO 30 DAYS AFTER THE AWARD OF

CONTRACT AND AS NEEDED

THEREAFTER.

FSRM COR 1 0

CO 1 0

(A) TOTAL 0 2 0 (B) TOTAL

1. THE CONTRACTOR MUST SUBMIT THE PERSONNEL RESUME, NO LATER THAN 30 DAYS AFTER THE AWARD OF CONTRACT AND AS

NEEDED THEREAFTER.

2. THE GOVERNMENT WILL REVIEW AND APPROVE OR REJECT WITH COMMENTS WITHIN 10 BUSINESS DAYS AFTER RECEIPT.

3. THE CONTRACTOR MUST UPDATE AND RESUBMIT THE PERSONNEL RESUME OR PROPOSE AN ALTERNATIVE PERSONNEL RESUME

WITHIN 5 BUSINESS DAYS.

LEVEL OF REPAIR ANALYSIS

DID-MR-001

3.1 This report describes the results of the Contractor's LORA program and documents in detail, the specific LORA tasks performed, how they were performed, and the results of performing the tasks.

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

8.1 Format. The list must be in the Contractor’s format. The deliverable must be presented in electronic 2010 MS Office Standard.

8.2 Content. The LORA report must include a discussion of the LORA performed.

A. A description of the maintenance alternatives addressing the core components of the access controls, surveillance, perimeter intrusion detection, and gate operator systems recommended by the contractor.

B. The contractor’s level of repair or discard recommendation for each item undergoing LORA must be specified.

C. The report must include a brief discussion of the compatibility of the LORA recommendations with the operations (both performance and support) and technical (reliability and maintainability design factors) requirements of the system.

D. Identification of any economic benefits under interim contractor support, contractor logistics support, reliability improvement warranty, or any other form of contractor repair must be identified.

E. A discussion of the sensitivity of LORA decisions which include as part of the sensitivity analysis and identification of the detrimental aspects of choosing alternatives, other than those selected as optimum, when economic, non-economic, and operational advantages that were taken into account must be included.

F. Recommendations for updating any maintenance and logistic support planning factors must be identified. Any recommendations made for updating planning factors related to maintenance and logistic support based on the LORA. In addition, the established operational and readiness requirement limitations and effects that were taken into account when making level of repair and discard recommendations must be identified.

G. A discussion of the similar systems and their maintenance structure, which were compared against the system under analysis, and identification of constraints that were levied against the similar systems, which influenced level of repair, and discard decisions on those systems must be included.

H. Identification of specific components and assemblies, which have established maintenance structures that are to be used by the system under analysis, must be identified.

I. The report must contain an indication and discussion of how current the LORA source data is for the similar system, recommendations for updating maintenance and other logistic elements and planning factors for the system under analysis, based on LORAs conducted on the similar systems being reviewed.

J. A description of problems, conclusions, assumptions, exceptions, and actions required must be specified.

CONTRACTORS PERSONNEL ROSTER TBD TBD

AD-004 CONTRACTORS PERSONNEL ROSTER N/A

N/A N/A NO 30 DAYS AFTER AWARD OF

CONTRACT AND 5 BUSINESS

DAYS AFTER ANY CHANGE

FSRM COR 1

CO 1

(A) TOTAL 0 2 0 (B) TOTAL

1. THE CONTRACTOR MUST SUBMIT THE FIRST CONTRACTORS PERSONNEL ROSTER, NO LATER THAN 30 DAYS AFTER AWARD OF CONTRACT AND 5 BUSINESS DAYS AFTER ANY CHANGE. IN ADDITION TO THE ROSTER UPDATE, THE CONTRACTOR MUST IMMEDIATELY NOTIFY THE COR AND CO OF PERSONNEL THAT HAVE BEEN REMOVED FROM THE ROSTER TO FACILITATE THE VOIDING OF ACCESS CONTROL CREDENTIALS. FAA CONTRACTOR PERSONNEL SECURITY POLICY MUST BE MET AT ALL TIMES.

2. THE GOVERNMENT WILL REVIEW AND COMMENT OR APPROVE OF THE CONTRACTORS PERSONNEL ROSTER WITHIN 30 BUSINESS

DAYS AFTER RECEIPT.

3. THE CONTRACTOR MUST UPDATE AND RESUBMIT THE CONTRACTORS PERSONNEL ROSTER, AS REVISIONS OCCUR WITHIN 10 DAYS

FOR APPROVEL.

STATUS OF GOVERNMENT FURNISHED EQUIPMENT (GFE)

REPORT

DID-PM-001

3.1 This report describes status and supply condition data about Government Furnished Equipment (GFE), which the contractor has received under the contract. This report will be used to review the condition, installation and effectiveness of the GFE.

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

8.1 Format. The list must be in the Contractor’s format. The deliverable must be presented in electronic 2010 MS Office Standard file.

8.2 Content. The report must contain the following information:

a. Contract Number

b. List of Government Furnished Equipment by Nomenclature.

c. National Stock Number of each equipment

d. Serial and Part Number of each equipment

e. Quantity of each equipment

f. Unit Acquisition Cost of each equipment

g. Condition of each equipment. in accordance with the equipment condition status listed below:

1. Serviceable Usable Without Qualification. New, used, repaired, or reconditioned equipment, which is serviceable and usable without limitation or restriction.

2. Serviceable Usable With Qualification. New, used, repaired, or reconditioned equipment which is serviceable and useable for its intended purpose but which is restricted from issue to specific units, activities, or Geographical areas by reason of its limited usefulness or short service-life expectancy.

3. Serviceable Test/Modification. Serviceable equipment, which requires test, alteration, modification, conversion or disassembly. This does not include items, which must be inspected or tested immediately prior to issue.

4. Unserviceable Reparable. Economically reparable equipment, which requires repair, overhauls, or reconditioning.

5. Unserviceable Incomplete. Equipment requiring additional parts or components to complete the end item prior to issue.

6. Unserviceable Condemned. Equipment, which has been determined to be unserviceable and cannot be repaired.

7. Unserviceable Reclamation. Equipment determined to be unserviceable, uneconomically reparable as a result of physical inspection, tear down, or engineering decision. Item contains serviceable components or assemblies to be reclaimed.

g. Status of use of the Government Furnished Equipment.

h. Solutions of problems relating to g.6 and g.7 above.

i. Request for assistance for repair of the GFE, as necessary.

EQUIPMENT/SYSTEMS MODIFICATION TBD TBD

CM-001 EQUIPMENT/SYSTEMS MODIFICATION N/A

N/A N/A NO 30 DAYS AFTER AWARD OF

CONTRACT AND

QUARTERLY

1. THE CONTRACTOR MUST SUBMIT THE EQUIPMENT/SYSTEMS MODIFICATION REPORT, NO LATER THAN 30 DAYS AFTER AWARD OF

CONTRACT AND QUARTERLY THEREAFTER.

2. THE GOVERNMENT WILL REVIEW AND COMMENT OR APPROVE OF THE EQUIPMENT/SYSTEMS MODIFICATION REPORT WITHIN 30

3. THE CONTRACTOR MUST UPDATE AND RESUBMIT THE EQUIPMENT/SYSTEMS MODIFICATION REPORT, AS REVISIONS OCCUR

WITHIN 10 DAYS FOR APPROVEL.

RECEIPT OF GFE REPORT

DID-PM-002

3.1 The Receipt of Government Furnished Equipment Report provides receipt data of transferred GFE to the Contractor from the previous CMC Contractor. This Data Item Description (DID) enables the FAA to maintain accurate fiscal and physical audit trails for all Government equipment received by the contractor.

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

8.1 Format. The list must be in the Contractor’s format. The deliverable must be presented in electronic 2010 MS Office Standard.

8.2 Content. The Receipt of Government Materiel Report must contain the following:

• Receiving Contract Number: DTFAWA number

• Shipping Contractor Number: DTFAWA number of material source contractor.

• FAA Material Inventory Form:

• National Stock Number CNSN) (CC 8-22). The NSN of item received if applicable.

• Unit of Issue.

• Quantity Received.

• Document Number (CC 30-43). Document number under which this materiel was received.

• Contract Line Item Number against Contractor Acquired Property (CAP) requested

• Condition of the materiel received as specified on the shipping document.

• Date of receipt. Example: 31 Jan 2016.

AS-BUILT MATERIALS LIST TBD TBD

CM-002 AS-BUILT MATERIALS LIST N/A

N/A N/A NO AS REQUIRED AFTER AN

APPROVED AS-BUILT

1. THE CONTRACTOR MUST SUBMIT THE AS-BUILT MATERIALS LIST, NO LATER THAN 10 DAYS AFTER AN APPROVED AS-BUILT. THE AS-BUILT MATERIALS LIST MUST BE SUBMITTED WITH DATA THAT ADDRESSES THE WORK ORDER THE AS-BUILT OCCURRED UNDER. IN ADDITION TO THE FAC ID, DATE, AND ANY MODIFICATIONS/RED LINES TO

FACILITY AS-BUILT DRAWINGS AND CONFIGURATION DOCUMENTATION.

2. THE GOVERNMENT WILL REVIEW AND COMMENT OR APPROVE OF THE AS-BUILT MATERIALS LIST WITHIN 30 DAYS

AFTER RECEIPT FROM CONTRACTOR.

3. THE CONTRACTOR MUST UPDATE AND RESUBMIT THE AS-BUILT MATERIALS LIST, AS REVISIONS OCCUR WITHIN 10

DAYS FOR APPROVEL.

TECHNICAL AND MANAGEMENT WORK PLAN

DID-PM-003

3.1 The Technical and Management Work Plan describes the

contractor’s plan to implement the statement of work (SOW) tasking provided via delivery order or task order. Additionally, it addresses contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements.

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

8.1 Format. The plan must be in a format that the contractor devises and conforms to the following:

a. Identification. The plan must be identified with the preparing office or contractors title, the identifying numbers or designation of the Contract/Procurement Request, the identify and/or nomenclature of the system/component/program/project, the security classification and the Government activity issuing the controlling contract.

b. Descriptive material. As may be needed to clarify or explain matters in the text, the plan may include descriptive material, sketches, drawings, photographs, tables, forms, graphs, worksheets, charts, etc.

c. Page size. The plan may be printed on standard size paper, e.g., 8 ½ x 11 inches or metric A4. The pages must be sequentially numbered and security bound together. As necessary, graphic material may be one-way fold-outs. All attachments must be identified and referenced in the text. Each section and paragraph must be numbered.

d. Table of contents and index. Plans of more than 30 pages in length must contain a table of contents.

Plans more than 120 pages in length must also include an Index.

e. Legibility. The document must be legible and reproducible.

f. The deliverable must be presented in electronic format MS Word version 2010 MS Office Standard.

8.2 Content. The plan must identify the contractor’s name, contractor number, title and number of the delivery or task order, security classification of the plan, name of contract monitor and the Government office issuing the tasking. The plan must include descriptive material, system diagrams, sketches, photographs, tables, forms, graphs, worksheets, charts, drawings, etc.

The plan must include the contractor’s approach to completing the delivery and information necessary for the Government to assess the soundness of the contractor’s approach. The plan must contain the following:

I. Organizational structure. The plan must include a description of the contractor’s organizational structure and assignment of functions, duties, and responsibilities, which will be assigned in the support of the tasking. Additionally, the plan must identify the contractor’s procedures, policies, and reporting requirements established to initiate, monitor, control, complete, and report on activities required of the delivery or task order.

II. Program management. The plan must present an organizational chart and supporting narrative describing the management office the contractor establishes to manage the contractual commitments. The plan must define the direct lines of control, responsibilities, functional relationships, and authority between the management office and the contractor’s other organizational elements. The plan must also describe all interfaces between the contractor and the Government and between the contractor and other contractors, which are necessary and pertinent to the accomplishment of contractual tasks, projects and programs.

III. Organizational Interfaces. The plan must describe all interfaces between the contractor and the government. Also between the other contractors and subcontractors which are necessary to complete the assign tasking. This must include a description of the applicable reasonability’s and functional relationships between those organizations.

IV. Methodology. The plan must include a narrative description clearly defining the technical approach (or method) including tools, standards, and procedures to be used by the contractor to accomplish the delivery or task order.

V. Personnel. The plan must list the personnel staffing of the contractor’s management office that directs the contractual tasks. The listing must include the education, training, skills, experience, and security clearance that personnel require to fill each such position and must state the identity, background, and work experience of the personnel assigned to fill these positions. The plan must also describe the staffing required for proper accomplishment of each contractual task by skill type, skill level, number of personnel, and security clearance. When submitted as part of a proposal, the plan must state how many such personnel are currently available and how many new hires are required to staff fully to accomplish each task as scheduled.

I. Security. Provide a Standard Practice Procedure (SPP) which fully describes the security program, safeguards emergency procedures to be established to the protection of Government-furnished and contractor-developed sensitive or classified materials prepared in conjunction with the contract. The SPP must be prepared in accordance with guidelines contained in the SIR. The SPP must require approval by the Government.

II. Schedule. The plan must include a milestone chart(s) graphically depicting the schedule of events associated with the delivery or task order. The level of detail must be sufficient to clearly show how each subtask must be performed. This includes:

a. Contractor activities

b. Contractor deliveries (interim and final)

c. Other program milestones as appropriate (including Government input)

d. Periodic milestones to allow adequate Government review of contractor progress

III. Resource chart. The plan must include a resource chart that graphically and numerically identifies the contractor’s total planned technician workforce and level of effort (LOE) and LOE by month for each subtask identified in the delivery or task order.

IV. Contractor request data. The plan must include the contractor’s best assessment of any additional data required by the contractor. This list must be detailed as possible and must include document titles, responsible Government organizations, and responsible Government contractors. The criticality of each data required must be identified.

V. Deliverables. The plan must include a brief description on the contents of each deliverable to be provided as a result of the delivery or task order. It must describe the management methods the contractor will employ to ensure meeting all preparations, format, and submittal requirements established by the CDRL (DD Form 1423) for data to be delivered to the Government.

VI. Other subjects to be included are as follows:

a. design control

b. reliability

c. configuration control

d. standardization

e. quality assurance

f. provisioning

g. control of Government property

h. delivery procedures

i. tests

j. certifications

k. packaging

l. shipping

m. other

MODIFICATIONS TO AS-BUILT FACILITY

DRAWINGS

TBD TBD

CM-003 MODIFICATIONS TO AS-BUILT FACILITY DRAWINGS N/A

N/A N/A NO AS MODIFICATIONS ARE TAKING

PLACE DURING REPAIR

FSRM COR 0 0

CO 0 0

(A) TOTAL 0 0 0 (B) TOTAL

15. TOTAL OF A & B 0

1. ALL CHANGES TO OR ADDITIONS TO BUILDINGS, STRUCTURES, AND RELATED EQUIPMENT AND SYSTEMS MADE BY THE CONTRACTOR MUST BE RECORDED AS REDLINES TO FACILITY DRAWINGS BY THE CONTRACTOR DURING EACH REPAIR.

CONTRACTORS RISK MANAGEMENT PLAN

DID-PM-004

3.1 The Contractor’s Risk Management Plan will be used to monitor management, cost and schedule of the contract efforts relative to a system and equipment. This information will provide the government with risk data for all risks associated with the system/equipment.

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

8.1 Format. The plan must be in contractor’s format. The deliverable must be presented in electronic 2010 MS Office Standard file.

8.2 Content. The plan must contain a cover and title page identifying the following:

a. Plan date of issue

b. Plan document number/revision number or letter

c. Contract number

d. Contractor name and address

e. Title of plan

f. Program title

g. Security classification, if classified

h. Distribution statement

i. Destruction notice

8.3. Revision Control. The plan must contain a list of all revisions identifying the following information:

a. Each revision number or letter

b. Date of each revision

c. Pages affected by each revision

8.4. Table of Contents. The table of contents must identify each major section title, paragraph number, and starting page number for each major section.

8.5. Contents. The plan must address in depth each major section identified below:

a. Introduction

b. Scope

c. Program Summary

d. Risk Management Strategy and Process

e. Responsible /Executing Organizational Component

f. Risk Management Process and Procedures

g. Risk Identification

h. Risk Analysis

i. Risk Mitigation Planning

j. Risk Mitigation Implementation

k. Risk Tracking

l. Figure(s) and Table (s)

COST PERFORMANCE REPORT TBD TBD

FD-001 COST PERFORMANCE REPORT N/A

N/A N/A NO MONTHLY

1. THE CONTRACTOR MUST SUBMIT THE COST PERFORMANCE REPORT, NO LATER THAN 30 DAYS AFTER AWARD OF CONTRACT AND

MONTHLY THEREAFTER.

2. THE GOVERNMENT WILL REVIEW AND COMMENT OR APPROVE OF THE COST PERFORMANCE REPORT WITHIN 30 DAYS AFTER

RECEIPT FROM CONTRACTOR.

3. THE CONTRACTOR MUST UPDATE AND RESUBMIT THE COST PERFORMANCE REPORT WITHIN, AS REVISIONS OCCUR WITHIN 10

CONTRACT SUMMARY REPORT

DID-PM-005

3.1 This report summarizes all work performed under the contract.

7.1 This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract.

8.1 Format. Document must be prepared on 8.5 x 11 inch paper and the deliverable must be presented in electronic 2010 MS Office Standard file. The data indicated below must be contained on the title page:

a) Type of Report, Final

b) Purchase Description Title

c) Contract Number

d) Dates of the Reporting Period

e) Security classification and distribution limitation markings must be included on all pages.

8.2. Content.

a) Table of Contents.

b) Brief summary of all work accomplished, to include both negative and positive results. All information must be referenced to the appropriate Progress Report, or section of the Final Report, where the subject is discussed in detail.

c) The body of the report must describe all work accomplished, including as applicable, test procedures, test results, and drawings, charts, graphs, illustrations, or other material needed to clarify the presentation.

d) Conclusions, recommendations, and proposals.

e) Appendixes for any necessary tables, references, photographs, charts, and illustrations.

MAN HOURS REPORT TBD TBD

FD-002 MAN HOURS REPORT N/A

1. THE CONTRACTOR MUST SUBMIT THE MAN HOURS REPORT, NO LATER THAN 30 DAYS AFTER AWARD OF CONTRACT AND

2. THE GOVERNMENT WILL REVIEW AND COMMENT OR APPROVE OF THE MAN HOURS REPORT WITHIN 30 DAYS AFTER RECEIPT

FROM CONTRACTOR.

3. THE CONTRACTOR MUST UPDATE AND RESUBMIT THE MAN HOURS REPORT WITHIN, AS REVISIONS OCCUR WITHIN 10 DAYS FOR

APPROVEL.

QUALITY SYSTEM PLAN

DID-QA-001

3.1 The Quality System Plan document describes the contractor’s plan, procedures, and controls that will be used to satisfy the requirements for Call Center ISO Q9001:2008 certification or registration, and to substantiate Program Management, Logistics Support, and Repair product quality and fulfillment of contract requirements during all phases of the contract.

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

8.1 Format. The list must be in the Contractor’s format. The deliverable must be presented in electronic 2010 MS Office Standard file.

8.2 Content. The Quality System Plan must describe the overall plan, procedures and controls that the Contractor will use to provide and maintain a satisfactory quality system as specified by ISO 9001:2008. The QSP must address four areas specifically:

1. Program Management

2. Logistics Support

3. Call Center (ISO 9001:2008 Certified or Registered)

4. Technician Repair Actions

LOGISTICS SUPPORT PLAN TBD TBD

ILS-001 LOGISTICS SUPPORT PLAN N/A

N/A N/A NO 30 DAYS AFTER AWARD AND UPDATES

AS REQUIRED

1. THE CONTRACTOR MUST SUBMIT THE LOGISTICS SUPPORT PLAN, NO LATER THAN 30 DAYS AFTER AWARD OF CONTRACT AND

UPDATES AS NEEDED THEREAFTER.

2. THE GOVERNMENT WILL REVIEW AND COMMENT OR APPROVE OF THE LOGISTICS SUPPORT PLAN WITHIN 30 DAYS AFTER RECEIPT

3. THE CONTRACTOR MUST UPDATE AND RESUBMIT THE LOGISTICS SUPPORT PLAN, AS REVISIONS OCCUR WITHIN 10 DAYS FOR

ANNUAL DIRECTIONS TO FACILITIES

DID-QA-002

3.1 Direction Letter to Facilities will contain Contractor description of the contract and the use of the contract by each facility. The letter will be sent annually and be updated to address modifications and/or additional operations issues after review and approval by the Program Office

(FSRM).

The Contractor must confirm receipt of the directions letter by any facility that utilizes the contract prior to conducting repairs.

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

The following is a guideline for the content and format of the directions letter to each facility. The Contractor may propose different content and format for FAA FSRM Program Office review. <<>> indicate fields that should be tailored for each facility letter with the latest data provided by the FSRM Program Office.

Contract Number Contract Name Contractor Name, Address, Phone Number

Date Letter is Issued

Federal Aviation Administration

«FAC_NAME»

«Mailing_Address»

«CITY», «STATE» «ZIP_CODE»

Attention: Facility Manager and Security Coordinator «Manager and FSC name)»

Subject: Corrective Maintenance Services of Physical Security Systems required by the FAA ASH Servicing Security Element (SSE) for «FAC_NAME»

Contract Guidance Letter to Supported Facilities Reference: Contract <<DTFAWA-xx-x-xxxxx>> Dear «FSC », <<Name of Contractor>> is pleased to inform you that on <<Date>> the FAA exercised Option Year X of the Corrective Maintenance Contract III (CMC III) <<DTFAWA-xx-x-xxxxx>> under the FAA Facility Security Risk Management (FSRM) Program. Use of the contract by each facility is contingent upon positive receipt of this letter by the facility manager and/or facility security coordinator.

This letter is issued in accordance with contract requirements and provides process guidelines for services under this contract including:

Hours of operation What types of security systems and security equipment are eligible for corrective maintenance, Help desk contact information, The service call process, and Corrective maintenance Work Order tracking process.

“Corrective maintenance services are funded from the FAA Operations budget and are subject to available funding. At times, the FSRM Program Office may have to limit services supplied under this contract if adequate funding is not available. The facility should contact the FSRM Program Office for details of contract limitations if necessary.”

“Note that the Corrective Maintenance contract does not cover sites that are under F&E project warranty.

Questions about warranty coverage should be directed to the FSRM Program Office COR for the Security System Design and Implementation contract.

Help Desk Contact Information and Hours of Operation <<Name of Contractor>>has established dedicated toll free numbers available 24/7 for CMC III to provide the central point of contact for reporting and coordinating repairs under this contract. The CMC III Help Desk toll free number(s) are:

<<Call Desk Phone Numbers>>

Repair Services Hours of Operation Per contract requirements, corrective maintenance services are provided during specific hours which are defined as:

<< Tier One hours, 24/7>>

<<Non Tier One hours, Mon – Fri (excluding Federal Holidays) 7:00am – 6:00pm>>

“The following table identifies the equipment that is eligible for support under this contract and systems and equipment that are not.”

Systems And Equipment Addressed By This Contract

Systems And Equipment Not Addressed By This Contract Include

Automated Access Control Systems Facility Security Fences/Gate Infrastructure

Video Surveillance Systems Facility Lighting Intrusion Detection Systems (integrated and stand-alone)

Facility Security Keys, Cores, and Electronic Entry Cards

Perimeter Intrusion Detection Systems Facility Door Infrastructure Security Intercom and Access Video Systems (ECV, GCV)

X-Ray Machines

Metal Detectors Portable Security Equipment Facility Security Barrier Arms and Security Gate Operators.

Fire Life Safety Systems (including systems with integrated intrusion detection capabilities) Elevator Controls

“The scope of repairs on barrier arms and gates is limited to the controllers and the electronic interfaces associated with the controllers. Repairs under the CMC III contract do not include replacing fencing structures, outside conduits, welds, rollers, etc. Specifically, repairs are limited to the following:

A. Failed security systems that control or report barrier arm and security gate status B. Failed Gate Operators”

For facilities with co-located Child Care Facilities, the scope of equipment covered is as follows:

Within Scope Out of Scope

CCTV at main entrance Remote entrance control at main entrance in coordination with CCTV Cipher lock at main entrance

Electrical Access Controls CCTV at other than the main entrance

IDS

Service Call Process “<<Name of Contractor>> provides corrective maintenance services for both “Tier One” and “Non Tier One” security equipment. Tier-One sites with equipment deployed by the FAA Facility Security Risk Management

(FSRM)

Program under the FAA SSI or SSDI contract are considered “standard” sites.

All service calls are coordinated through the CMC III Help Desk by contacting the toll free number above.

(Notes: do not contact local <<Name of Contractor>> offices for corrective maintenance to security systems covered under this contract. The FAA program office will not pay for costs of repair services that are not initiated and coordinated through the CMC II Help Desk.

For systems still covered under warranty from the FAA FSRM Program Office, please contact the FSRM Program Office (AJW-246) SSDI COR.

Requests for reconfiguration, modifications (additions, deletions) of existing security systems must be submitted as NAP F&E project requests to the FSRM Program Office (AJW-246) SSDI COR. The CMC III may NOT be used to reconfigure or modify existing systems.

The following describes the service call process from problem identification through closure.

1. Someone at the FAA site identifies a problem with the security systems and equipment covered under this contract and notifies the Facility Manager, the Facility Security Coordinator (FSC) or their delegate.

2. The Facility Manager, the FSC, or their delegate contacts the CMC III Help Desk. The caller should be prepared to provide the following facility identification information to the CMC III Help Desk. The information on record for your site is:

Facility ID: «FAC_ID» Tier 1/Non Tier 1: «Tier One/Non Tier One» Facility Location: «LOC_ID» Facility Type: «FAC_TYPE» Facility Address: «ADDRESS1»

«CITY», «STATE» «ZIP_CODE»

3. The CMC III Help Desk dispatcher will validate that the site is covered under the CMC III contract and that the reported problem is associated with the systems and equipment addressed by this contract.

4. The CMC III Help Desk dispatcher will record the name and contact information for the caller as well as the name and number of the person to be contacted to coordinate a repair visit (if different from the caller).

5. The CMC II Help Desk dispatcher will then open a unique Work Order for this reported problem. This unique WO number will be used by the facility in all communications regarding the repair.

6. The CMC II Help Desk dispatcher will contact the appropriate on-call Security Technician, who in turn (within two hours of the initial call) contacts the FAA POC (or designee) to get a more detailed description of the problem.

7. Working with the FAA POC, the Security Technician determines the correct repair priority response times (see response timetables below).

8. The Security Technician then attempts to evaluate the issue over the phone to determine a) if the issue can be resolved over the phone or b) what replacement parts, if any, may be required to be preordered from the <<Name of Contractor>> Logistics Center. Site personnel will not be asked to do any maintenance or repair but some problems may be resolved without requiring a site visit (such as problems with operating the system that can be addressed with instructions from the technician or problems that can be resolved with a reset or power cycle on some piece of equipment).

9. The Security Technician then coordinates any required site visit with the FAA POC.

10. The Security Technician travels to the site at the time coordinated with the FAA POC. Upon arrival, the Security Technician will contact the FAA site representative before performing any work. At this point, the site representative should let the technician know who at the facility will be approving the work order once completed. The Security Technician will keep the FAA site representative fully informed of the corrective maintenance repair status, and an estimated service restoration time.

11. The Security Technician then performs the corrective maintenance, including coordinating with the <<Name of Contractor>> Logistic Support to obtain parts needed for repair.

12. Once the repair is completed, the Security Technician will perform system tests, and complete any outstanding inventory actions. At the conclusion of these activities, the Security Technician will get approval of the work from the FAA facility-designated POC or their delegate who has been authorized to approve work order completion. The approver will be asked to sign a copy of the work order. At this point, the work order may have handwritten notes about the work completed. After getting a signature from the authorized site representative, the technician will call the CMC III Help Desk to update the status of the work order to “Complete”. The technician then submits a work order summary to the CMC II Help Desk who puts that information in the database and e-mails a final copy of the completed work order to the POC.

Response Times from Contract Statement of Work

<<Tier One Response Times by Equipment Category>>

<<Non Tier One Response Times by Equipment Category>>

Security Gate and Barrier Arm Additional Maintenance Requirements The security gate and security barrier arm systems must follow the required corrective maintenance procedures on an as-soon-as-possible timeline. However, upon initial assessment, if the Contractor determines obsolete or non-standard equipment is needed to complete repairs or the timeline exceeds two weeks the Contractor must execute an escalation plan.

Corrective Maintenance Work Order Tracking Process Sites can call the CMC III Help Desk 24/7 to get the status of their work orders. In addition, the FAA CO, COTR, SMRs and Facility Security Coordinators (FSCs) will have access to Work Order status through a <<web application>>.

The <<web application>> allows authorized users to view Work Order status and search work order information for a specific site or set of sites. All information can be exported to Excel or other formats for further evaluation.

Users can search all repair events tracking information including but not limited to Facility ID, repair ticket number, FAA POC, Security Technician, or date. The Service Portal is accessible via the following web address:

<<web address>> A user ID and password is required to access the <<web application>>.