Attachment 1 - Statement of Work - 70Z03822QJ0000229.pdf
PDF 515 KB Posted
- Attached to
- Input/Output Configuration for Refreshed Data Concentrator Unit Federal contract opportunity
- Solicitation number
- 70Z03822QJ0000229
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Attachment 2 - Terms and Conditions - 70Z03822QJ0000229.pdf | ||
| Attachment 3 - Justification and Approval For Other Than Full and Open Competition - 70Z03822QJ0000229.pdf |
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
Statement of Work (SOW) for MH-60T
Refreshed Data Concentrator Unit (DCU-R)
Input/Output (I/O) Configuration
Transition
Attachment 1 – Statement of Work – 70Z03822QJ0000229
Purchase Order Number: TBD
Purchase Order: TBD
MH-60T Refreshed Data Concentrator Unit Input/Output Configuration Transition Statement of Work
TABLE OF CONTENTS
GENERAL
Background
Objective
Scope
Period of Performance
DOCUMENTS
Applicable Documents
PROJECT MANAGEMENT
Roles and Responsibilities
SCI Technology, Inc
USCG Aviation Logistics Center (ALC)
Government Furnished Equipment (GFE)
Required GFE
REQUIREMENTS
Contractor Technical Support
Software Development
Software
I/O Configuration File
Hardware Delivery
Testing
Documentation
Version Description Document
Load Procedure
Interface Control Document (ICD) Markups
Contract Deliverables
LIST OF ACRONYMS
Appendix A. “CDRLs”
GENERAL
Background
The United States Coast Guard (USCG) operates the MH-60T Jayhawk helicopter to conduct its missions. Since the first MH-60T flight in 2007, the USCG has completed several interim upgrades to the Common Avionics
Architectural System (CAAS) Operational Flight Program (OFP) software in order to integrate additional equipment, additional functionality, and enhance Human-Machine Interface (HMI). Currently the fielded Data
Concentrator Unit (DCU) that has been in production for several years is now experiencing issues that are no longer repairable due to the obsolescence of replacement components and has reached end of life. The Refreshed Data
Concentrator Unit (DCU-R) is the recommended replacement as a Form, Fit, and Function replacement.
Additionally, due to a complete avionics refreshed component, a transition of MH-60T I/O configuration file to the
DCU-R is required to complete testing.
Objective
The objective of the activities outlined within this Statement of Work (SOW) is to successfully deliver a airworthy representative, workable MH-60T DCU-R, Part Number 5561000-001, loaded with the MH-60T I/O configuration file for System Integration Lab (SIL) demonstration and testing by the USCG to evaluate the DCU-R compatibility with the existing DCU, Part Number 544300-001. The DCU-R, P/N 5561000-001, is to be furnished by the USCG.
Scope
This SOW is to be accomplished under contract (To be determined at time of award). The terms and conditions of the base contract apply. The requirements defined herein are as detailed in subsequent paragraphs; port the existing
DCU I/O configuration file to the DCU-R for demonstration/evaluation purposes.
Period of Performance
After award of contract and initial kickoff and requirements review, period of performance for delivery of a workable MH-60T DCU-R ported with existing DCU I/O configuration file is 16 weeks.
DOCUMENTS
Applicable Documents
Technical documents applicable to this contract are identified in Table 2. The list is comprised of the latest version of the documents existing at the time of contract issuance. In the event that a new version of a document is released, the Contractor shall use the latest version available. Other documents that may apply include internal
SCI Technology, Inc. (SCI) developed system documents, commercial and military specifications and standards.
Table 2: Applicable Documents
Number Title Source
5443000-001 DCU Top Level Assy Drawing (latest) SCI
5561000-001 DCU-R Top Level Assy Drawing (latest) SCI
3989-A007-001 HH-60J DCU Electrical Interface Control Document
(EICD) (F)
USCG
3989-A008-001 HH-60J DCU Multiplex Interface Control Document
(MICD), (G)
USCG
PROJECT MANAGEMENT
Roles and Responsibilities
SCI Technology, Inc.
SCI Technology, Inc shall serve as the principal design authority for the porting of the existing DCU I/O configuration file to the DCU-R. As such, SCI Technology, Inc. shall provide any software that is required to load the OFP and I/O Configuration files into the DCU-R.
USCG Aviation Logistics Center (ALC)
The ALC MRR product line shall serve as the Government representative and technical point of contact for the porting of the existing DCU I/O configuration file to the DCU-R. ALC shall acquire all system equipment. ALC shall manage the installation of equipment in the aircraft and any required aircraft modifications. During all portions of the aircraft integration, the USCG is responsible for supporting the aircraft. The USCG will provide the aircraft crew, all aircraft maintenance, all aircraft fuel, and all aircraft supplies. The aircraft shall remain the property of the USCG and shall not be bailed to the Contractor.
Government Furnished Equipment (GFE)
The Contractor shall utilize GFE managed under contract TBD.
Required GFE
The Government will provide the Contractor with the additional GFE listed in Table 3.
Table 3: Government Furnished Equipment
Nomenclature Part Number Qty Estimated Value
DCU-R 5561000-01 2 $70,000
REQUIREMENTS
Contractor Technical Support
Contractor shall provide off-site support to the USCG to answer question and discuss any issues found during the
USCG demonstration/evaluation test effort.
Software Development
Software
DCU-R Operational Flight Program
Contractor is to utilize the latest development version of the CH-47F Operational Flight Program (OFP) in support of the USCG demonstration/evaluation test effort. The USCG shall be notified of any updates that may occur, as a result of the on-going CH-47F effort, during the USCG effort. The USCG and Contractor will decide if they updates are pertinent to the USCG effort and if the USCG should update.
Integration Release (IR) is acceptable for all deliveries.
The USCG is not responsible for any update direction of the OFP during this effort. The USCG will report any issues found during the demonstration/evaluation test effort and discuss with the Contractor any potential path forward.
Support Software
The Contractor shall provide any software that is required to load the OFP and I/O Configuration files into the
DCU-R.
I/O Configuration File
The Contractor is port the MH-60T I/O configuration file, part number 5443797-004 Rev J, to the DCU-R I/O configuration file. The Contractor will provide all the required changes to make the I/O configuration file work with the DCU-R
There are two planned IR releases to be delivered: 1) initial IR release 2) second IR release with any I/O configuration corrections for issues found during the initial USCG demonstration/evaluation test.
1. IR #1 delivery shall be loaded into the two delivery units and bench tested prior to shipping to the USCG.
2. IR #2 and any subsequent deliveries are to be electronic deliveries. The USCG load the DCU-R unit’s on-sight for testing.
Hardware Delivery
The Contractor is to utilize GFE for the DCU-R deliveries. The USCG will arrange for the GFE through PM
Cargo.
The Contractor shall ship the DCU-Rs utilizing DD1149s to the following address:
U.S. Coast Guard Aviation Logistics Center (ALC) 1664 Weeksville Road MRR Product Line Division, Bldg. 79 Elizabeth City, NC 27909-5001 Attn: Contracting Officer and Contracting Officer Representative (COR)
While the hardware is in the possession of the USCG, the USCG will assume all responsibility for any damage or repair if ensued during the time of custody and or testing. At the completion of USCG testing, the USCG will return the DCU-Rs to the Contractor. The Contractor is responsible returning the DCU-Rs to PM Cargo.
Testing
The Contractor shall perform operational bench checkout of DCU-R for MH-60T DCU-1 and DCU-2 configurations.
Documentation
Version Description Document
The Contractor shall provide a Version Description Document (VDD) for each delivery of OFP and I/O
Configuration file.
Load Procedure
The Contractor shall provide a load procedure providing sufficient information on how to load the DCU-R with
OFP and I/O Configuration files, including any cabling documentation, required software, and system requirements.
Interface Control Document (ICD) Markups
The Contractor shall provide markups (or separate change description) to the EICD (3989-A007-001) and MICD
(3989-A008-001) for any changes between the DCU (5443000-001) and the DCU-R (5561000-001) e.g. xtra bits, Least Significant Bit (LSB) value, etc.
Contract Deliverables
The contract deliverables requirement list (CDRL) for this effort are detailed in 6.0 Appendix A. The Contractor shall provide the following deliveries and all deliveries, other than hardware, shall be in electronic format delivered via the Contractor’s secure File Transfer Protocol (FTP) site.
LIST OF ACRONYMS
Acronym Definition
ALC Aviation Logistic Center
CAAS Common Avionics Architecture System
CDRL Contract Data Requirement List
COR Contract Officer Representative
DCU Data Concentrator Unit
DCU-R Refreshed Data Concentrator Unit
EICD Electrical Interface Control Document
FTP File Transfer Protocol
GFE Government Furnished Equipment
HMI Human-Machine Interface
ICD Interface Control Document
I/O Input/Output
IR Integration Release
LSB Least Significant Bit
MICD Multiplex Interface Control Document
MRR Medium Range Recovery
OFP Operational Flight Program
SIL Software Integration Lab
SOW Statement of Work
SW Software
USCG U. S. Coast Guard
VDD Version Description Document
APPENDIX A. “CDRLS”
Contract Deliverable Requirement List
CDRL Title Frequency/
Qty
Acceptance
Required Delivery Timing
SOW
Reference
A001 DCU-R Hardware 2 As required 4.4
A002 Reserved
A101
OFP
(Electronic Form) As required With hardware delivery 4.3.1.1
A102 Program loading Software
(Electronic Form) As required
1 week prior to any subsequent SW delivery 4.3.1.2
A103
I/O Configuration File
(Electronic Form)
IR1 Bailment Unit
IR2 Electronic Field Load
IR1 w/ hardware delivery.
IR2 as required 4.3.2
A104 Version description Document As required With each SW delivery 4.6.1
A105 Software load Procedure As required X 1 week prior to subsequent
SW delivery 4.6.2
A106 ICD Change Information As required X 1 week prior to with each SW delivery 4.6.3
A107 Reserved
File details come from the government source that posted it. Updated .