80 FR 13401 - Cooperative Research and Development Agreement-Coast Guard Response Boat-Medium Data Recorder
DEPARTMENT OF HOMELAND SECURITY
Coast Guard Federal Register Volume 80, Issue 49 (March 13, 2015)
Coast Guard
Federal Register Volume 80, Issue 49 (March 13, 2015)
| Page Range | 13401-13403 | |
| FR Document | 2015-05418 |
[Federal Register Volume 80, Number 49 (Friday, March 13, 2015)] [Notices] [Pages 13401-13403] From the Federal Register Online [www.thefederalregister.org] [FR Doc No: 2015-05418] ----------------------------------------------------------------------- DEPARTMENT OF HOMELAND SECURITY Coast Guard [Docket No. USCG-2015-0145] Cooperative Research and Development Agreement--Coast Guard Response Boat-Medium Data Recorder AGENCY: Coast Guard, DHS. ACTION: Notice of intent; request for comments. ----------------------------------------------------------------------- SUMMARY: The Coast Guard announces its intent to enter into a Cooperative Research and Development Agreement (CRADA) with Vector Controls, Inc. (Vector) to develop changes to the response boat-medium (RB-M) onboard engine data bus that will convert Society of Automotive Engineers (SAE) J1939 format to the National Marine Electronics Association (NMEA) 0183/2000 data format. A test schedule has been proposed in which Vector will develop and install the required RB-M control system software upgrades and relevant additional equipment; a Coast Guard field unit will operate the RB-M in normal operations; and the Coast [[Page 13402]] Guard Research and Development Center (R&DC) will install a dedicated data recorder system and conduct periodic data downloads for demonstration purposes. While the Coast Guard is currently considering partnering with Vector, the Coast Guard solicits public comment on the possible nature of and participation of other parties in the proposed CRADA. In addition, the Coast Guard also invites other potential non- Federal participants, who have the interest and capability to bring similar contributions to this type of research, to consider submitting proposals for consideration in similar CRADAs. DATES: Comments must be submitted to the online docket via http://www.regulations.gov, or reach the Docket Management Facility, on or before April 13, 2015. Synopses of proposals regarding future CRADAs must reach the Coast Guard (see FOR FURTHER INFORMATION CONTACT) on or before April 13, 2015. ADDRESSES: Submit comments using one of the listed methods, and see SUPPLEMENTARY INFORMATION for more information on public comments.Online--http://www.regulations.gov following Web site instructions. Fax--202-493-2251. Mail or hand deliver--Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590-0001. Hours for hand delivery are 9 a.m. to 5 p.m., Monday through Friday, except Federal holidays (telephone 202-366-9329). FOR FURTHER INFORMATION CONTACT: If you have questions on this notice or wish to submit proposals for future CRADAs, contact Jay Carey, Project Official, Surface Branch, U.S. Coast Guard Research and Development Center, 1 Chelsea Street, New London, CT 06320, telephone 860-271-2702, email [email protected]. If you have questions on viewing or submitting material to the docket, call Cheryl Collins, Program Manager, Docket Operations, telephone 202-366-9826, toll free 1-800-647-5527. SUPPLEMENTARY INFORMATION: Public Participation and Request for Comments We encourage you to submit comments and related material on this notice. All comments received will be posted, without change, to http://www.regulations.gov and will include any personal information you have provided. Do not submit detailed proposals for future CRADAs to the Docket Management Facility. Instead, submit them directly to the Coast Guard (see FOR FURTHER INFORMATION CONTACT) . Comments should be marked with docket number USCG-2015-0145 and should provide a reason for each suggestion or recommendation. You should provide personal contact information so that we can contact you if we have questions regarding your comments; but please note that all comments will be posted to the online docket without change and that any personal information you include can be searchable online (see the Federal Register Privacy Act notice regarding our public dockets, 73 FR 3316, Jan. 17, 2008). Mailed or hand-delivered comments should be in an unbound 8\1/2\ x 11 inch format suitable for reproduction. The Docket Management Facility will acknowledge receipt of mailed comments if you enclose a stamped, self-addressed postcard or envelope with your submission. Documents mentioned in this notice, and all public comments, are in our online docket at http://www.regulations.gov and can be viewed by following the Web site's instructions. You can also view the docket at the Docket Management Facility (see the mailing address under ADDRESSES) between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. Discussion CRADAs are authorized under 15 U.S.C. 3710(a).\1\ A CRADA promotes the transfer of technology to the private sector for commercial use, as well as specified research or development efforts that are consistent with the mission of the Federal parties to the CRADA. The Federal party or parties agree with one or more non-Federal parties to share research resources, but the Federal party does not contribute funding. --------------------------------------------------------------------------- \1\ The statute confers this authority on the head of each Federal agency. The Secretary of DHS's authority is delegated to the Coast Guard and other DHS organizational elements by DHS Delegation No. 0160.1, para. II.B.34. --------------------------------------------------------------------------- CRADAs are not procurement contracts. Care is taken to ensure that CRADAs are not used to circumvent the contracting process. CRADAs have a specific purpose and should not be confused with other types of agreements such as procurement contracts, grants, and cooperative agreements. Under the proposed CRADA, the R&DC will collaborate with one non- Federal participant. Together, the R&DC and the non-Federal participant would develop the changes required to convert the current engine data format used on the USCG RB-M (Society of Automotive Engineers (SAE) J1939) to a widely used format in marine electronics (NMEA 0183/2000). The RDC will provide Vector access to an operational RB-M at a Coast Guard field unit on or about May 1, 2015. The Coast Guard plans to operate a dedicated data recorder system on the RB-M for 90 days then return the vessel to its standard operational configuration. We anticipate that the Coast Guard's contributions under the proposed CRADA will include the following: (1) Develop the demonstration test plan to be executed under the CRADA; (2) Provide the test vessel, test vessel support, facilities, and all required approvals as required for a 90-day demonstration under the CRADA; (3) Conduct a Privacy Threshold Analysis (PTA) as required for the demonstration to be conducted under this CRADA; (4) Conduct a Privacy Impact Assessment as required for the demonstration to be conducted under this CRADA; (5) Collect and analyze demonstration test plan data in accordance with the CRADA demonstration test plan; and (6) Develop the Demonstration Final Report, which will document the methodologies, findings, conclusions, and recommendations of this CRADA work. We anticipate that the non-Federal participants' contributions under the proposed CRADA will include the following: (1) Provide any equipment and software upgrades required to conduct the demonstration as described in the demonstration test plan developed under this CRADA; (2) Provide technical oversight as required to conduct the demonstration as described in the demonstration test plan developed under this CRADA; (3) Provide the technical data package for all equipment, including dimensions, weight, power requirements, interface specifications, and other technical considerations for the additional components to be utilized under this CRADA; (4) Provide shipment and delivery of all equipment required for the demonstration to be conducted under this CRADA; and (5) Provide travel and other associated personnel and other expenses as required. The Coast Guard reserves the right to select for CRADA participants all, some, or no proposals submitted for this CRADA. The Coast Guard will provide [[Page 13403]] no funding for reimbursement of proposal development costs. Proposals and any other material submitted in response to this notice will not be returned. Proposals submitted are expected to be unclassified and have no more than five single-sided pages (excluding cover page, DD 1494, JF-12, etc.). The Coast Guard will select proposals at its sole discretion on the basis of: (1) How well they communicate an understanding of, and ability to meet, the proposed CRADA's goal; and (2) How well they address the following criteria: (a) Technical capability to support the non-Federal party contributions described; and (b) Resources available for supporting the non-Federal party contributions described. Currently, the Coast Guard is considering Vector for participation in this CRADA. This consideration is based on the fact that Vector has demonstrated its technical ability as the developer and manufacturer of the current RB-M propulsion control system. However, we do not wish to exclude other viable participants from this or future similar CRADAs. This is a technology demonstration effort. The goal of this CRADA is to develop the changes required to convert the current data format used on the USCG RB-M (J1939) to a widely used format in marine electronics (NMEA 0183/2000). Special consideration will be given to small business firms/consortia, and preference will be given to business units located in the U.S. This notice is issued under the authority of 5 U.S.C. 552(a). Dated: February 24, 2015. B.N. Macesker, Executive Director, U.S. Coast Guard Research and Development Center. [FR Doc. 2015-05418 Filed 3-12-15; 8:45 am] BILLING CODE 9110-04-P
![Federal Register / Vol. 80, No. 49 / Friday, March 13, 2015 / Notices 13401
DHS IT Security Program Handbook. contest its content, may submit a trains that enter or exit the United States
This handbook establishes a request in writing to CBP’s FOIA and from the individuals upon crossing
comprehensive program, consistent Officer, 1300 Pennsylvania Avenue the U.S. border.
with federal law and policy, to provide NW., Washington, DC 20229. Basic information is obtained from
complete information security, When seeking records about yourself individuals, the individual’s attorney/
including directives on roles and from this system of records or any other representative, CBP officials, and other
responsibilities, management policies, CBP system of records your request federal, state, local, and foreign
operational policies, and application must conform with the Privacy Act agencies.
rules, which will be applied to regulations set forth in 6 CFR part 5.
EXEMPTIONS CLAIMED FOR THE SYSTEM:
component systems, communications You must first verify your identity,
between component systems, and at meaning that you must provide your full No exemption shall be asserted with
interfaces between component systems name, current address, and date and respect to information maintained in the
and external systems. place of birth. You must sign your system that is collected from a person or
One aspect of the DHS comprehensive request, and your signature must either submitted on behalf of a person, if that
program to provide information security be notarized or submitted under 28 person, or his or her agent, seeks access
involves the establishment of rules of U.S.C. 1746, a law that permits or amendment of such information.
This system, however, may contain
behavior for each major application, statements to be made under penalty of
information related to an ongoing law
including NIIS. These rules of behavior perjury as a substitute for notarization.
enforcement investigation because the
require users to be adequately trained While no specific form is required, you
information regarding a person’s travel
regarding the security of their systems. may obtain forms for this purpose from
and border crossing was disclosed to
These rules also require a periodic the Director, Disclosure and FOIA,
appropriate law enforcement in
assessment of technical, administrative, http://www.dhs.gov or 1–866–431–0486.
conformance with the above routine
and managerial controls to enhance data In addition you should:
uses. As such pursuant to 5 U.S.C.
integrity and accountability. System • Explain why you believe the
552a(j)(2) and (k)(2), DHS will claim
users must sign statements Department would have information on
exemption from (c)(3); (e)(8); and (g) of
acknowledging that they have been you;
the Privacy Act of 1974, as amended, as
trained and understand the security • Identify which component(s) of the
is necessary and appropriate to protect
aspects of their systems. System users Department you believe may have the
this information.
must also complete annual privacy information about you;
awareness training to maintain current • Specify when you believe the Dated: February 27, 2015.
access. records would have been created; and Karen L. Neuman,
NIIS transactions are tracked and can • Provide any other information that Chief Privacy Officer, Department of
be monitored. This allows for oversight will help the FOIA staff determine Homeland Security.
and audit capabilities to ensure that the which DHS component agency may [FR Doc. 2015–05804 Filed 3–12–15; 8:45 am]
data is being handled consistent with all have responsive records. BILLING CODE 9111–14–P
applicable federal laws and regulations If your request is seeking records
regarding privacy and data integrity. pertaining to another living individual,
you must include a statement from that DEPARTMENT OF HOMELAND
RETENTION AND DISPOSAL:
individual certifying his/her agreement SECURITY
NIIS data is subject to a retention for you to access his/her records.
requirement. The information collected Without this bulleted information Coast Guard
and maintained in NIIS is used for entry CBP may not be able to conduct an [Docket No. USCG–2015–0145]
screening, admissibility, and benefits effective search, and your request may
purposes and is retained for seventy-five be denied due to lack of specificity or Cooperative Research and
(75) years from the date obtained. lack of compliance with applicable Development Agreement—Coast
However, NIIS records that are linked to regulations. Guard Response Boat-Medium Data
active law enforcement lookout records, In processing requests for access to Recorder
CBP matches to enforcement activities, information in this system, CBP will
and/or investigations or cases will review not only the records in the Coast Guard, DHS.
AGENCY:
remain accessible for the life of the law operational system but also the records Notice of intent; request for
ACTION:
enforcement activities to which they that were replicated on the unclassified comments.
may become related. The current and classified networks, and based on SUMMARY: The Coast Guard announces
disposition for paper copy is 180 days this notice provide appropriate access to its intent to enter into a Cooperative
from date of departure. Records the information. Research and Development Agreement
replicated on the unclassified and
RECORD ACCESS PROCEDURES: (CRADA) with Vector Controls, Inc.
classified networks will follow the same
See ‘‘Notification procedure’’ above. (Vector) to develop changes to the
retention schedule.
response boat-medium (RB–M) onboard
SYSTEM MANAGER AND ADDRESS: CONTESTING RECORD PROCEDURES: engine data bus that will convert
Assistant Commissioner, Office of See ‘‘Notification procedure’’ above. Society of Automotive Engineers (SAE)
Information Technology, U.S. Customs J1939 format to the National Marine
RECORD SOURCE CATEGORIES:
mstockstill on DSK4VPTVN1PROD with NOTICES
and Border Protection Headquarters, Electronics Association (NMEA) 0183/
1300 Pennsylvania Avenue NW., The system contains certain data 2000 data format. A test schedule has
Washington, DC 20229. received on individuals, passengers and been proposed in which Vector will
crewmembers that arrive in, depart develop and install the required RB–M
NOTIFICATION PROCEDURE: from, or transit through the United control system software upgrades and
Individuals seeking notification of States. This system also contains relevant additional equipment; a Coast
and access to any record contained in information collected from carriers that Guard field unit will operate the RB–M
this system of records, or seeking to operate vessels, vehicles, aircraft, and/or in normal operations; and the Coast
VerDate Sep<11>2014 19:27 Mar 12, 2015 Jkt 235001 PO 00000 Frm 00080 Fmt 4703 Sfmt 4703 E:\FR\FM\13MRN1.SGM 13MRN1](https://thefederalregister.org/doc/80_FR_13450/page/1.svg)
![Federal Register / Vol. 80, No. 49 / Friday, March 13, 2015 / Notices 13403
no funding for reimbursement of Council (PWSRCAC) as an alternative procedures, applicants submit a letter
proposal development costs. Proposals voluntary advisory group for Prince requesting recertification that includes a
and any other material submitted in William Sound, Alaska. This description of any substantive changes
response to this notice will not be certification allows the PWSRCAC to to the information provided at the
returned. Proposals submitted are monitor the activities of terminal previous triennial recertification.
expected to be unclassified and have no facilities and crude oil tankers under the Further, public comment is not solicited
more than five single-sided pages Prince William Sound Program prior to recertification during
(excluding cover page, DD 1494, JF–12, established by statute. streamlined years, only during the
etc.). The Coast Guard will select DATES: This recertification is effective triennial comprehensive review.
proposals at its sole discretion on the for the period from March 1, 2015
basis of: On March 1, 2003, the Coast Guard
through February 28, 2016.
(1) How well they communicate an was transferred from the Department of
FOR FURTHER INFORMATION CONTACT: LT
understanding of, and ability to meet, Transportation (DoT) to the Department
Tom Pauser, Seventeenth Coast Guard of Homeland Security (DHS) and
the proposed CRADA’s goal; and District (dpi), by phone at (907) 463–
(2) How well they address the retained the previous delegations that
2812, email thomas.e.pauser@uscg.mil
following criteria: were provided while it was in the DoT.
(a) Technical capability to support the or by mail at P.O. Box 25517, Juneau,
Alaska 99802. The Alyeska Pipeline Service
non-Federal party contributions Company pays the PWSRCAC $2.9
described; and SUPPLEMENTARY INFORMATION:
(b) Resources available for supporting million annually in the form of a
Background and Purpose longterm contract. In return for this
the non-Federal party contributions
described. As part of the Oil Pollution Act of funding, the PWSRCAC must annually
Currently, the Coast Guard is 1990, Congress passed the Oil Terminal show that it ‘‘fosters the goals and
considering Vector for participation in and Oil Tanker Environmental purposes’’ of OPA 90 and is ‘‘broadly
this CRADA. This consideration is Oversight and Monitoring Act of 1990 representative of the communities and
based on the fact that Vector has (the Act), 33 U.S.C. 2732, to foster a interests in the vicinity of the terminal
demonstrated its technical ability as the long-term partnership among industry, facilities and Prince William Sound.’’
developer and manufacturer of the government, and local communities in The PWSRCAC is an independent,
current RB–M propulsion control overseeing compliance with nonprofit organization founded in 1989.
system. However, we do not wish to environmental concerns in the Though it receives federal oversight like
exclude other viable participants from operation of crude oil terminals and oil many independent, non-profit
this or future similar CRADAs. tankers. organizations, it is not a federal agency.
This is a technology demonstration On October 18, 1991, the President
The PWSRCAC is a local organization
effort. The goal of this CRADA is to delegated his authority under 33 U.S.C.
that predates the passage of OPA 90.
develop the changes required to convert 2732(o) to the Secretary of
The existence of the PWSRCAC was
the current data format used on the Transportation in E.O. 12777, section
8(g) (see 56 FR 54757; October 22, 1991) specifically recognized in OPA 90
USCG RB–M (J1939) to a widely used where it is defined as an ‘‘alternate
format in marine electronics (NMEA for purposes of certifying advisory
councils, or groups, subject to the Act. voluntary advisory group.’’
0183/2000). Special consideration will
be given to small business firms/ On March 3, 1992, the Secretary Alyeska funds the PWSRCAC, and the
consortia, and preference will be given redelegated that authority to the Coast Guard makes sure the PWSRCRC
to business units located in the U.S. Commandant of the USCG (see 57 FR operates in a fashion that is broadly
This notice is issued under the authority 8582; March 11, 1992). The consistent with OPA 90.
of 5 U.S.C. 552(a). Commandant redelegated that authority
to the Chief, Office of Marine Safety, Recertification
Dated: February 24, 2015.
Security and Environmental Protection By letter dated February 24, 2015, the
B.N. Macesker, (G–M) on March 19, 1992 (letter #5402).
Executive Director, U.S. Coast Guard Commander, Seventeenth Coast Guard
On July 7, 1993, the USCG published
Research and Development Center. certified that the PWSRCAC qualifies as
a policy statement, 58 FR 36504, to
[FR Doc. 2015–05418 Filed 3–12–15; 8:45 am] clarify the factors that shall be an alternative voluntary advisory group
BILLING CODE 9110–04–P considered in making the determination under 33 U.S.C. 2732(o). This
as to whether advisory councils, or recertification terminates on February
groups, should be certified in 28, 2016.
DEPARTMENT OF HOMELAND accordance with the Act. Dated: February 24, 2015.
SECURITY The Assistant Commandant for D.B. Abel,
Marine Safety and Environmental
Coast Guard Rear Admiral, U.S. Coast Guard Commander,
Protection (G–M), redelegated Seventeenth Coast Guard District.
[USCG–2015–0083] recertification authority for advisory
[FR Doc. 2015–05806 Filed 3–12–15; 8:45 am]
councils, or groups, to the Commander,
Prince William Sound Regional Seventeenth Coast Guard District on BILLING CODE 9110–04–P
Citizens’ Advisory Council Charter February 26, 1999 (letter #16450).
Renewal
mstockstill on DSK4VPTVN1PROD with NOTICES
On September 16, 2002, the USCG
AGENCY: Coast Guard, DHS. published a policy statement, 67 FR
ACTION: Notice of recertification. 58440, that changed the recertification
procedures such that applicants are
SUMMARY: The purpose of this notice is required to provide the USCG with
to inform the public that the Coast comprehensive information every three
Guard has recertified the Prince William years (triennially). For each of the two
Sound Regional Citizens’ Advisory years between the triennial application
VerDate Sep<11>2014 19:27 Mar 12, 2015 Jkt 235001 PO 00000 Frm 00082 Fmt 4703 Sfmt 9990 E:\FR\FM\13MRN1.SGM 13MRN1](https://thefederalregister.org/doc/80_FR_13450/page/3.svg)
Document Created: 2015-12-18 11:42:29
Document Modified: 2015-12-18 11:42:29
| Category | Regulatory Information | |
| Collection | Federal Register | |
| sudoc Class | AE 2.7: GS 4.107: AE 2.106: | |
| Publisher | Office of the Federal Register, National Archives and Records Administration | |
| Section | Notices | |
| Action | Notice of intent; request for comments. | |
| Dates | Comments must be submitted to the online docket via http:// www.regulations.gov, or reach the Docket Management Facility, on or before April 13, 2015. | |
| Contact | If you have questions on this notice or wish to submit proposals for future CRADAs, contact Jay Carey, Project Official, Surface Branch, U.S. Coast Guard Research and Development Center, 1 Chelsea Street, New London, CT 06320, telephone 860-271-2702, email [email protected] If you have questions on viewing or submitting material to the docket, call Cheryl Collins, Program Manager, Docket Operations, telephone 202-366-9826, toll free 1-800-647-5527. | |
| FR Citation | 80 FR 13401 |
2024 Federal Register | Disclaimer | Privacy Policy
USC | CFR | eCFR