PWS_for_RMS_Support.pdf

PDF 147 KB Posted

Attached to
T-38 Engineering Services Federal contract opportunity
Solicitation number
FA8211-13-R-3004
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Hill Air Force Base

About this file

PWS for RMS support

View the file

Other files for this federal contract opportunity

Other files attached to T-38 Engineering Services, newest first.
File Type Posted
FA821113R3004_______0002.pdf PDF
FA821113R3004_______0001.pdf PDF
PWS_for_IATPandLESS.pdf PDF
2013_CDRLs_IATPandLESS.pdf PDF
PWS_for_BASIC.pdf PDF
FA821113R3004.pdf PDF
2013_CDRLs_FEM.pdf PDF
2013_CDRLs_BASIC.pdf PDF
2013_CDRLs_STRESS.pdf PDF
2013_CDRLs_RMS_Support.pdf PDF
PWS_for_STRESS.pdf PDF
AF_Proposal_Adequacy_Checklist.pdf PDF
PWS_for_FEM.pdf PDF
Show all 13

On GovTribe

Work with this file on GovTribe

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

Text version

PERFORMANCE WORK STATEMENT

For the:

T-38 Reliability, Maintainability, and Supportability (RM&S) Contractor Support

20 May 2013

Prepared by:

Eric Flygare

OO-ALC/GHMEB

(801) 775-6225 eric.flygare@hill.af.mil

Michael Blinn

OO-ALC/GHMEJ

(801)777-0535 michael.blinn@hill.af.mil

OGDEN AIR LOGISTICS COMPLEX

AIRCRAFT SUSTAINMENT GROUP

ENGINEERING DIVISION

MECHANICAL SYSTEMS SECTION

HILL AIR FORCE BASE, UTAH 84056

i T38 RM&S Support Last Rev. Date: 20 May 2013

TABLE OF CONTENTS

Page

LIST OF TABLES .......................................................................................................................... ii RECORD OF REVISIONS ........................................................................................................... iii

1.0 DESCRIPTION OF SERVICES

1.1 Scope

1.2 Period of Performance

2.0 SERVICE SUMMARY

3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1 Reports Provided

3.2 Security and Access to Government Facilities and Equipment

4.0 GENERAL INFORMATION

4.1 General Requirements

4.2 Specific Requirements

4.2.1 Contractor Services

4.2.2 Integrated Management Support

4.2.3 Management System Requirements

4.2.4 Contractor Task Order Management Requirements

5.0 APPENDICES AND ATTACHMENTS

5.1 Applicable Documents

5.1.1 Document Availability and Delivery

5.2 Applicable CDRLs

5.2.1 CDRL List

5.2.2 Contractor Reporting

ACRONYMS AND ABBREVIATIONS

ATTACHMENT ONE: LIST OF APPLICABLE DOCUMENTS .......................................... A1-1 ATTACHMENT TWO: TASK REQUEST FORM ................................................................. A2-1 ATTACHMENT THREE: APPLICABLE CDRLS ................................................................. A3-1 ii T38 RM&S Support

LIST OF TABLES

Page

Table 1 – Service Summary for T-38 RM&S Contractor Support Table 2 – Task Categories Table 3 – CDRL List for the RM&S Contractor Support ......................................................... A3-1 iii T38 RM&S Support

RECORD OF REVISIONS

REV DATE PAGE(S)

AFFECTED

SECTION

AFFECTED REASON FOR REVISION

- 18 May 2012 n/a n/a Original PWS date of release.

1 20 May 2013 Multiple Changed date to current date

1 20 May 2013 1 4.2.2.1 Update paragraph to include man-hour documentation requirements.

1 20 May 2013 1 A1-1 Included note identifying references are applicable in their entirety

1 T38 RM&S Support

1.0 DESCRIPTION OF SERVICES:

The following Performance Work Statement (PWS) provides a description of the required contractor services in support of the T-38 Aircraft Structural Integrity Program (ASIP), T-38 Mechanical Systems Integrity Program (MECSIP), T-38 Avionics Integrity Program (AVIP), T-38 Mature and Proven Aircraft Branch (MAPA), T-38 System Program Office (SPO), Air Education and Training Command (AETC), and other T-38 related commands.

The T-38 SPO at Ogden ALC, UT, is responsible for the reliability, availability, safety, and mission readiness of the T-38 Talon trainer jet. The T-38 Talon is a twin engine, high altitude, supersonic jet trainer used in a variety of roles because of its design, economy of operations, ease of maintenance, high performance, and exceptional safety record. AETC is the primary user of the T-38 for missions such as:

1) Specialized Undergraduate Pilot Training (SUPT), Introduction to Fighter Fundamentals (IFF), and 3) Euro-NATO Joint Jet Pilot Training (ENJJPT). Air Combat Command (ACC), Air Force Materiel Command (AFMC), the National Aeronautics and Space Administration (NASA), the U.S. Navy, and foreign militaries also use the T-38 in various roles. The T-38 requires multiple integrity programs to ensure the overall weapon system safety, suitability, and effectiveness (or OSS&E).

The T-38 aircraft is currently being managed with the benefit of both the experience and historical analyses available from the Northrop Grumman Corporation (NGC), the Original Equipment Manufacturer (OEM). The T-38 SPO requires the ability to collect and analyze data from Global Combat Support System (GCSS) and other government database systems to identify potential systems and related key components that may require action to prevent negative impact on Mission Capability (MC) rates and Fleet Availability (FA). The goal of this PWS is to propose continued OEM support to the T-38 SPO for the Reliability, Maintainability and Supportability (RM&S) of the T-38. The scope of RM&S includes support for sustainment of weapon system operational safety, suitability, and effectiveness. This proposed contract would allow the SPO to continue to contact the OEM by phone or email, cite the specific task order and task number, and receive rapid input from the OEM.

T-38 weapon system RM&S is dependent upon multiple disciplines to ensure weapon system’s viability for the future. This effort allows direct access to the Northrop T-38 research engineers, design engineers, test and evaluation engineers, sustainment engineers, logisticians, OEM data research, and other technical capabilities found within NGC. The extensive RM&S analysis and engineering experience within NGC as performed on other major weapon systems would provide critical and timely support for system analysis and sustainment of the T-38 and allow the SPO to re-establish a “cradle-to-grave” T-38 weapon system management approach. Analysis and support includes but is not limited to technology application evaluations, analysis of alternatives, requirements development, operational utility evaluations, proto-type design, design development, test and evaluation, configuration analysis and support, 2 T38 RM&S Support durability, safety, reliability, supportability, failure modes and consequences, cost of ownership, sustainment improvements, deficiency and mishap evaluations, analytical condition inspections (ACIs), and maintenance support. This approach would maximize the SPO’s ability to ensure that the T-38 fleet meets availability, cost, and capability benchmarks required to satisfy its Air Force mission and remain viable to the end of the programmed life cycle.

1.1 Scope:

The Contractor shall provide the appropriate level of engineering support to address all CDRL deliverables as described in this PWS. Tasks will be assigned by either the Government Program Manager or the Engineering Lead and may include, but are not limited to, the following activities:

• Conduct engineering analysis, design, test, and sustainment activities as required by T-38 SPO.

• Provide RM&S analyses and studies into areas impacting availability, maintainability, sustainability and cost as required by the SPO.

• Provide engineering and RM&S support for Product Improvement Working

Group (PIWG) like activities as required.

• Provide system integrity engineering analysis support as required by T-38

Program Office and/or Integrity Manager and/or Chief Engineer.

• Analysis and support of technology application evaluations, analysis of alternatives, requirements development, operational utility evaluations, proto-type design, design development, test and evaluation, configuration analysis and support, durability, safety, reliability, supportability, failure modes and consequences, cost of ownership, sustainment improvements, deficiency and mishap evaluations, analytical condition inspections, and maintenance support.

• Any other engineering tasks that are either too small for an individual task orders or for which schedule constraints preclude establishing a new task order.

1.2 Period of Performance:

The period of performance for this PWS is 12 months.

2.0 SERVICE SUMMARY:

Table 1 describes the Service Summary for the tasks as outlined in this PWS. Most of the efforts as described in this PWS will be engineering services and program management related.

3 T38 RM&S Support

Table 1 – Service Summary (SS) for the T-38 RM&S Contractor Support

Performance Objectives PWS Reference

Performance Threshold (Minimum Acceptable)

Engineering Technical Activities: Contractor to provide support engineering analyses, assessments, and research towards accomplishment of this PWS.

4.2.1 through 4.2.4

For engineering analyses (or assessments or studies): All actions accomplished as required with no more than one disapproval by the Government for technical discrepancies per technical report. Any necessary corrections must be made within 30 days of Government notification" to the Performance Threshold column/Engineering Technical Activities row of the Service Summary.

Technical Documentation:

Contractor to generate timely, error free technical, management, and all other reporting and documentation;

includes activities such as monthly financial reporting, meeting minutes, etc.

4.2.1.2 through 4.2.4, 5.2.1, 5.2.2

95% of revisions are error free in the final product.

Preliminary documentation of the reports to be 90% error free.

3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES:

3.1 Reports Provided:

The Government will provide the contractor with all the necessary Government Technical Orders (TOs), Time Compliance Technical Orders (TCTOs), and contractor reports, required to accomplish the tasks as detailed in this PWS.

3.2 Security and Access to Government Facilities and Equipment:

3.2.1 Security Clearance: The efforts required for this task are UNCLASSIFIED and will not require Contractor personnel to obtain a security clearance. Contractor personnel shall abide by all Air Force rules, procedures, and standard of conduct. Contractors requiring access to Air Force Automated Information Systems (AIS) shall have background investigations and security awareness training completed prior to the start of contract performance. When the period of performance is complete and/or the contractor personnel leave work on this project, they will return all access cards and base identification badges within five days.

3.2.2 Access to Government Facilities: Access to Government facilities is limited.

Therefore, the contractor shall coordinate the need, time, and personnel requiring access to Government facilities with the Government Program Manager (PM), at least one week prior to need. The Government PM or designated representative will coordinate between the contractor and base personnel as required.

4 T38 RM&S Support

3.2.3 Access to Government Equipment: The Government PM will assist the contractor in obtaining the necessary clearance for access to Government equipment, as the program dictates.

4.0 GENERAL INFORMATION:

4.1 General Requirements:

The T-38 aircraft is currently being managed with the benefit of both the experience and historical analyses available from the Northrop Grumman Corporation (NGC), the Original Equipment Manufacturer (OEM). The SPO requires the ability to collect and analyze data from Global Combat Support System (GCSS) and other government database systems to identify potential systems and related key components that may require action to prevent negative impact on Mission Capability (MC) rates and Fleet Availability (FA). The goal of this effort is to provide vital and timely OEM support to the Reliability, Maintainability, and Supportability (RM&S) of the T-38. Scope of RM&S will include support for sustainment of weapon system operational safety, suitability, and effectiveness. Safety, suitability, and effectiveness will benefit from T-38 weapon system integrity analysis and support which is dependent upon multiple integrity disciplines to ensure weapon systems viability for the future. This PWS allows the T-38 SPO to contact the OEM by phone or email, cite the specific task order, and receive rapid input from the OEM.

4.2 Specific Requirements:

4.2.1 Contractor Services: The contractor shall provide the appropriate engineering, program management, and technical services as required for this PWS. Limited travel will be required to meet the goals of this effort.

4.2.1.1 Data Compatibility: All data will be presented in a format useable by Government entities. For example, the Government uses Microsoft Word, Adobe Acrobat, and similar word processing software.

4.2.1.2 Task Assignment:

4.2.1.2.1 Tasks shall be assigned by the Government and accepted by the contractor using the

Task Request Form (Attachment Two) with an individual WSMT number assigned to each task. The contractor shall not be required to accept tasks if the cost to execute them will result in exceeding the value of the contract.

4.2.1.2.2 Following assignment of a WSMT number the Contractor shall review and categorize each task according to the criteria in Table 2 Task Categories. Task category designation shall be subject to approval by the Government Program Manager.

4.2.1.2.3 Tasks categorized as Type I “Minor tasks” shall be assigned under one “task” number and submitted to the Contractor by either e-mail or telephone call.

5 T38 RM&S Support

Table 2 – Task Categories

Type Completion Time

Examples Deliverables Delivery Schedule for Deliverables

Authorization to Proceed

I <50 hours Minor Tasks such as:

• Requests for technical data

• Drawing revisions for CSI designations

• Preliminary investigations of problem reports

Planning documents (unless approved by Government Program Manager to move to a Type II category)

E-mail response directly to requestor, contractor format; cc to Government Program Manager

Coordinated with requestor Automatic upon receipt of task

II 50-325 hours Intermediate Tasks such as:

• Aft Canopy Study

• Follow-on investigations of problem reports

Project Plan, other deliverables as described in the Project Plan

Project Plan to be delivered within 20 business days unless previously approved by the Government Program Manager; other deliverables to be submitted as described in the Project Plan.

Automatic upon approval of Project Plan by the Government Program Manager

III 325-1000 hours

Major Tasks such as:

• Flight Loads Data

Collection

• PMP Baseline

Recovery

• Aft Fuselage

Hydraulic Coupling Analysis

Project Plan, ROM estimate, proposed task schedule, technical performance measures, other deliverables as described in the Project Plan

Project Plan to be delivered within 30 business days unless previously approved by the Government Program Manager; ROM estimate, proposed task schedule, and technical performance measures to be delivered 45-60 days following Government approval of Project Plan; other deliverables to be submitted as described in the Project Plan/task schedule.

Pending receipt of authorization to proceed letter from Contracting Office following delivery and approval of Project Plan, ROM estimate, proposed task schedule, and technical performance measures.

IV >1000 hours To be processed similar to Type III tasks but only after written direction from the Government Contracting Office.

6 T38 RM&S Support

4.2.1.2.4 Exceptions:

4.2.1.2.4.1 Any task requiring subcontractor support shall automatically be categorized as a Type

III task.

4.2.1.2.4.2 Any Type I task which, when evaluated, would require more than 90 days to complete shall be automatically categorized as a Type II task (subject to approval by the Government Program Manager).

4.2.1.2.4.3 The Contractor shall not proceed with any tasks submitted without a task number until written verification has been received from the Government Program Manager.

4.2.1.2 Data Documentation: All data researched for this project will be provided in the individual task order reports. Details of the reporting are as follows:

• For technical status reporting, the Contractor shall provide quarterly informal status reports to the Government Program Manager detailing how hours spent during the month were distributed among the assigned tasks. The status report shall identify the hours spent for each Type II or Type III task during the reporting month versus the hours allocated for the task. Type I tasks shall be lumped into one Type III task for reporting purposes, with a table included in the report which lists all Type I tasks assigned to date and the status of each, but with hours spent reported in aggregate. Type II and Type III tasks shall be listed individually. Report shall include a table listing all Type II and Type III tasks with a summary of hours spent to date. Report format shall be determined by the Contractor.

• For program management reporting, the Contractor shall provide quarterly status reporting on their tasks. The status report shall include a brief technical description of individual tasks, program management issues, and financial information (CDRL A039, Attachment Three).

• For engineering dispositions (other than those defined as Type I), the Contractor shall provide a final task report for individual dispositions, size to be commensurate with the amount of engineering activities involved, minimum to be completion of the task request form, Attachment Two. For larger efforts, a separate report might be required; this shall be determined on a case-by-case basis and coordinated with the Government Program Manager or Government lead engineer. Format for separate reports shall be according to CDRL A047, Attachment Three.

• At the conclusion of the Period of Performance (POP) for this effort, a final report is required, including a summary of each of the task orders of this PWS. The intention of this document is to catalogue the activities for the contract’s POP (CDRL A047, Attachment Three).

4.2.1.2.1 Task Specific Deliverables

7 T38 RM&S Support

4.2.1.2.1.1 Project Plan which includes the problem definition, a proposed plan to investigate and resolve problem, identification of any travel required, details of the proposed final deliverable(s) for the task, and identification of entrance and exit criteria for each milestone, Contractor format.

4.2.1.2.1.2 Rough-Order-of-Magnitude (ROM) estimate, Contractor format.

4.2.1.2.1.3 Proposed task schedule, prepared using Microsoft Project (.mpp file format, Contractor format).

4.2.1.2.1.4 Chart of Proposed Technical Performance Measures, Contractor format.

4.2.1.3 Formal Evaluations: The following formal evaluations are to be supported by the

Contractor:

1) Preliminary Program Review: A preliminary program review for the Contractor to present their refined “way ahead” for the RM&S support, and to further discuss the anticipated challenges with the tasks as described in this PWS, shall be held no later than two months ARO contract award. The Contractor shall provide a PPT document and meeting minutes as part of the first status report (CDRL A039, Attachment Three).

2) Final Program Review: A final program review for the Contractor to present their results and discuss the outcomes of their RM&S support shall be held sometime during the last month of the contract POP. The Contractor shall provide a PPT document and meeting minutes as part of the last status report (CDRL A039, Attachment Three).

4.2.1.4 Contractor Travel: The following are the Contractor travel requirements:

1) Miscellaneous Program Support Trips: The Contractor is authorized five miscellaneous trips for a maximum two people each trip (minimum one engineer), for up to five days (each trip) to any of the following locations: 1) Hill AFB, UT;

2) Randolph AFB, TX; 3) El Segundo, CA; 4) St. Augustine, FL; or 5) Southwest Research Institute (SwRI), San Antonio, TX. In addition, the Contractor should consider travel to other locations within the continental US that would be required in support of this PWS.

2) These trips are intended to provide the Contractor flexibility in supporting the RM&S activities; as such, there are no firm requirements. Miscellaneous trips shall be reported in the quarterly reports (CDRL A039, Attachment Two).

3) Type II, III, and IV individual tasks may require more than the five (5) trips listed above. Manhour or ROM estimates for those tasks shall clearly state the number of support trips required and cost for those trips. The requirement for additional support trips will be reviewed with the manhour or ROM estimate and approved or disapproved with the task. No additional funding will be provided for additional support trips.

8 T38 RM&S Support

4.2.2 Integrated Management Support:

4.2.2.1 Contractor Program Manager: For all tasks required by this PWS, the Contractor shall identify and maintain a program manager (PM). The program manager shall have a defined and direct line of authority and responsibility over all aspects of the work effort. The Contractor’s work progress, status and any corrective action shall be documented (CDRL A039, Attachment Two). The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.

4.2.2.2 Contractor Interim Reporting: The Contractor shall submit interim reports as appropriate with the requirements of each individual sub-task (see Para. 4.2.1.2).

4.2.3 Management Systems Requirements:

Management systems requirements are to be provided by the Contractor.

4.2.3.1 Continuation of Essential DoD Contractor Services During Crisis: The Contractor is responsible for ensuring provisions are in place to continue to provide the essential services of this program in times of crisis. The Contractor shall work with the Government to define those essential services, with these services defined in the first quarterly report (CDRL A039, Attachment Two).

4.2.4 Contractor Task Order Management Requirements: Task management by the

Contractor shall include but is not limited to:

4.2.4.1 Providing monthly informal status reports to the Government Program manager detailing how hours spent during the month were distributed among the assigned tasks.

4.2.4.2 Providing monthly cost-schedule-performance programmatic reports.

4.2.4.3 Participating in quarterly programmatic briefings.

4.2.4.4 All internal management reviews necessary for any deliverable required for Type II, Type III, or Type IV tasks.

4.2.4.5 Program management support.

4.2.4.6 Pricing for ROM estimates.

5.0 APPENDICES AND ATTACHMENTS:

http://www.ecmra.mil/

9 T38 RM&S Support

5.1 Applicable Documents:

5.1.1 Document Availability and Delivery: If the Government deems appropriate, the

Contractor may use other applicable documents. Also, the Contractor shall request necessary documents from the Government, as required. In turn, the Government shall supply all required TOs and TCTOs for the Contractor to perform the tasks of this PWS.

10 T38 RM&S Support

5.2 Applicable CDRLs:

5.2.1 CDRL List: The deliverable products (CDRL list) for this PWS are presented in

Table 2 (CDRLs A039 and A047, Attachment Two).

Note: See DD Form 1423 for further details.

5.2.2 Contractor Reporting: The Contractor shall submit reports in accordance with the

DIDs specified in DD form 1423 (CDRLs A039 and A047, Attachment Two) with the following stipulations. Tables, figures, drawings, etc. shall be placed immediately following their reference in the main body of the text (i.e. same page if possible or on the next page). Reports shall be submitted in a hard cover 3-ring binder. This will facilitate the report revision by allowing addition/replacement of individual pages without having to submit a completely new report. An electronic copy (of the number required in the DD Form 1423) of the final report shall be submitted in both Microsoft Word for Windows and Adobe Acrobat (.pdf) format to the T-38 Mechanical Systems section at AFLCMC/WLDMB.

11 T38 RM&S Support

ACRONYMS AND ABBREVIATIONS

ACC - Air Combat Command AETC - Air Education and Training Command AFB - Air Force Base AFMC - Air Force Materiel Command ALC - Air Logistics Center ARO - After Receipt of Order ASIP - Aircraft Structural Integrity Program AVIP - Avionics Integrity Program CCB - Configuration Control Board IMIS - Integrated Maintenance Information System MECSIP - Mechanical Systems Integrity Program OC-ALC - Oklahoma City Air Logistics Center PIWG - Product Improvement Working Group ROM - Rough Order of Magnitude TO - Technical Order USAF - United States Air Force

A1-1 T38 RM&S Support

ATTACHMENT ONE: LIST OF APPLICABLE DOCUMENTS

Department of Defense (DoD) Specifications:

1) Air Force Policy Directive 63-1, “Acquisition and Sustainment Life Cycle Management,” 3 April 2009.

2) Air Force Instruction 63-1001, “Aircraft Structural Integrity Program,” 18 April 2002.

Department of Defense (DoD) Standards:

3) MIL-STD-1530C, “Aircraft Structural Integrity Program,” 3 August 2010.

4) MIL-STD-1798, “Mechanical Equipment and Subsystem Integrity Program,” 24 January

2010.

5) MIL-HDBK-1783b(2), Engine Structural Integrity Program,” June 2009.

6) MIL-STD-1796A, “Avionics Integrity Program,” 13 October 2011.

Note: If the Government deems appropriate, the Contractor may use other applicable documents. Documents listed above are applicable in their entirety.

A2-1 T38 RM&S Support

ATTACHMENT TWO: TASK REQUEST FORM

Reliability, Maintainability

& Supportability Task Request Form

No.

Page: 1 of 18

Effective: 2 April 2013 Revision: B Approved:

Authorized documents are published online only - verify any copy against the online system before use

Section I – To be completed by Government Program Manager

Task No.:

Title:

Date Originated: Date Response Requested By:

Govt. Program Manager: Telephone No.:

Requestor: Telephone No.:

Deliverable Requested (report (size and format), analysis, drawing, etc.):

Initial Problem Description:

Task Category: I II III IV

Are there attachments with this form? Yes No If yes, list:

Section II – To be completed by NGTS personnel

Expanded Problem Description:

Investigation/Analysis/Testing:

Solutions/Recommendations:

Section III – To be completed by NGC personnel

Project Engineer: Date:

NGTS Project Manager: Date:

Date returned to Government Program Manager:

Manhours Used:

A3-1 T38 RM&S Support

ATTACHMENT THREE: APPLICABLE CDRLS

Table 3 – CDRL List for the T-38 RM&S Contractor Support

PWS Paragraph CDRL CDRL Description DID 4.2.1.2, 4.2.1.3, 4.2.1.4, 4.2.2.1, 4.2.3.1, 5.2.1, 5.2.2

A039 Contractor’s Progress, Status and Mgt Reports

DI-MGMT-80227

4.2.1.2, 5.2.1, 5.2.2 A047 Scientific and Technical Reports:

- Individual Task Order Reports

DI-MISC-80711A

T-38 Reliability, Maintainability, and Supportability (RM&S) Contractor Support
20 May 2013
4.2.1.1 Data Compatibility: All data will be presented in a format useable by Government entities. For example, the Government uses Microsoft Word, Adobe Acrobat, and similar word processing software.
ACRONYMS AND ABBREVIATIONS
Department of Defense (DoD) Specifications:
Department of Defense (DoD) Standards:

Table 3 – CDRL List for the T-38 RM&S Contractor Support

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