Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF NOVEMBER 30, 2011 FBO #3658
SOLICITATION NOTICE

D -- System Safety Oversight Support to the Program Manager (PM), Digital Fires Situational Awareness (DFSA) Target Location, Designation Hand-off System (TLDHS)

Notice Date
11/28/2011
 
Notice Type
Presolicitation
 
NAICS
541330 — Engineering Services
 
Contracting Office
M67854 MARINE CORPS SYSTEMS COMMAND 2200 Lester Street Quantico, VA
 
ZIP Code
00000
 
Solicitation Number
M6785412I2413
 
Response Due
12/29/2011
 
Archive Date
1/29/2011
 
Point of Contact
Sharon Edwards 703-432-3151 Sharon Edwards
 
E-Mail Address
2-3151<br
 
Small Business Set-Aside
N/A
 
Description
This is a Request for Information (RFI) that preceeds that actual solicitation. Please respond by 12/29/2011 with a Capability Statement for the requirement below. THIS IS NOT A REQUEST FOR FORMAL PROPOSALS. 1.0SCOPE The scope of this effort is to provide system safety oversight support to the Program Manager (PM), Digital Fires Situational Awareness (DFSA) Target Location, Designation Hand-off System (TLDHS) Project, of Product Group 11, Marine Corps Systems Command. The Contractor will follow the MIL-STD-882D guidance to eliminate or manage safety hazards, develop and update the safety documents, conduct software safety testing, incorporate and provide safety and warning devices, review procedures and training materials, report and manage safety risks, and perform limited software code quality assurance reviews in support of the Government Software Acceptance Testing. Execution will be done in accordance to the TLDHS requirements and MIL-STD-882D. Specific details of the scope and support required for this effort are further delineated in Section 5.0, 6.0 and 7.0. 2.0 BACKGROUND PM DFSA has the need for independent safety oversight as part of the TLDHS system safety systems engineering process, required by the DoDI 5000.2 and USD (AT&L) Memo dated Sep 23, 2004. The safety oversight support is used to eliminate environmental, safety, and occupational health (ESOH) hazards, or minimize their risks. 3.0 SYSTEM DESCRIPTION The TLDHS is a modular, man-portable digital fires system designed for the Forward Observer (FO), Forward Air Controllers (FACs), Fire Support Teams (FSTs), Firepower Control Teams (FCTs), Tactical Air Control Parties (TACP), and Reconnaissance Teams to quickly acquire targets in day, night, and near-all-weather visibility conditions, conduct precise, near-instantaneous artillery fire support, naval gunfire support, and digital close air support (CAS) with strike aircraft, such as the F/A-18, AV-8B, A-10 and F-16. Operators are able to accurately determine their own location as well as that of their targets, digitally transmit (hand-off) data to supporting arms elements for fire mission planning. This system interfaces with other Marine Air Ground Task Force (MAGTF) Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) platforms to exchanges digital fires data, such as the Joint Battle Command-Platform (JBC-P), Blue Force Tracker (BFT), Advanced Field Artillery Tactical Data System (AFATDS), Theater Battle Management Core Systems (TBMCS), Common Laser Range Finder (CLRF), Remote Video Viewing Terminal (RVVT), and Command and Control Personal Computer (C2PC). It is also inside the Combat Operations Center (COC), offering its capability to the Regimental or Division Air Officer. The Common Aviation Command and Control System (CAC2S) is also incorporating the software to get ground tracks into the Joint Range Extension Gateway (JRE-G) gate, much like the Direct Air Support Centers (DASC) are doing today. TLDHS is composed of a Military Ruggedized Tablet running StrikeLink ฎ software and associated equipment. Associated equipment includes the AN/PRC-117F/G radio, Power Distribution Device, CD DVD ฑ R/W drive, external USB hard drive and associated cables. The CLRF is an integral part of the operational system; however, it is not a component of the principle end item for TLDHS. 4.0 REFERENCE DOCUMENTS The following documents provide useful information on DoD Acquisition and Systems Engineering processes. In the event of conflict between the reference documents and this SOW, the SOW shall take precedence. However, nothing in this document supersedes applicable laws and regulations unless a specific exemption has been obtained. MIL-HDBK-881, Work Breakdown Structure Handbook, Jan 1998 USD (AT&L) Defense Acquisition System Safety Memo, Sep 23, 2004 USD (AT&L) Defense Acquisition System Safety “ Environment, Safety, and Occupational Health (ESOH) Risk Acceptance memorandum, Mar 2007 Department of Defense Instruction (DoDI) 5000.2, Operation of the Defense Acquisition System, Dec 2008 Marine Corps Operational and Organizational (O&O) Concept for the Target Location, Designation and Hand-off System, Change 6, Apr 2009 MIL-STD-882D, System Safety in Systems Engineering, Feb 2000 TLDHS Performance Specification, Aug 2011 National Environmental Policy Act (NEPA)/Executive Order (EO) 12114 ISO/IEC 9126 Software Engineering 5.0 SPECIFIC REQUIREMENT The Contractor Project Lead shall be DAWIA Level III certified in Systems Planning, Research, Development and Engineering (SPRDE) and Program Management or equivalent experience is required. The safety SME appointed by the Contractor Project Lead shall be DAWIA Level II certified in Systems Safety or equivalent experience is desired. The security requirement for this tasking will be Secret. All personnel under this Contract will be US citizens who are able to obtain and maintain security clearance at the secret level. It is anticipated that in the performance of this Contract, personnel may occasionally be required to handle classified material and access classified spaces. 6.0 CONTRACT MANAGEMENT 6.1 Project Lead The Contractor shall appoint a Project Lead for this effort. The Project Lead shall be DAWIA Level III certified in System Safety and Project Management or equivalent experience is required. The Project Lead shall coordinate all contractor activities and be the primary point of contact for all technical and project related communications between the Contractor and the TLDHS Project Management Office (PMO). 6.2 Safety Joint In Process Reviews (IPRs) The Contractor shall host and conduct co-chaired Safety IPRs on project topics of mutual interest, including specific items of special interest identified by the TLDHS PMO. These reviews shall be convened at the request of the TLDHS PMO. The Contractor shall prepare the agenda and meeting minutes for each review and deliver them to the TLDHS PMO. The Contractor shall provide the meeting agenda to the TLDHS PMO no later than (NLT) 5 business working days prior to the meeting. The meeting minutes shall be delivered to the TLDHS PMO for review NLT 5 business working days after the meeting is adjourned. The Project Lead shall co-chair IPR ™s with the TLDHS Systems Engineer. CDRL A001 “ Meeting Agenda CDRL A002 “ Meeting Minutes 6.3 Contract Status Reporting The Contractor shall provide a monthly status report that documents the status of the Contractor ™s efforts. The report shall also include funding, cost, and Work Breakdown Structure (WBS) data. The Contractor shall prepare and deliver the WBS NLT 10 working days After Contract Award (DACA). Changes to the WBS shall be reported in the Monthly Status Report. Trip reports are also required by the Contractor and due to the TLDHS PMO NLT 5 working days after the trip is completed. CDRL A003 - Contractor ™s Progress, Status and Management Report CDRL A004 - Contractor ™s WBS CDRL A005 - Trip Report 7.0 SYSTEM SAFETY IN SYSTEMS ENGINEERING The Contractor shall provide technical guidance and knowledge to the TLDHS PMO with respect to software design, safety engineering, software testing and integration. The Contractor will work with the TLDHS Prime Developer to ensure that software and safety quality standards are maintained. 7.1 System Safety Program Plan (SSPP) The Contractor shall develop and update the SSPP to document the safety system engineering processes. The SSPP is also the basis for the Programmatic Environment, Safety and Occupational Health Evaluation (PESHE). CDRL A006 “ SSPP 7.2 Safety Subject Matter Expert (SME) The Contractor shall be assigned as the SME for safety and will assist the TLDHS PMO in planning, managing and conducting the Safety Integrated Product Team (IPT). The SME shall perform all other safety related tasks identified by the TLDHS PMO. The safety SME shall provide guidance relative to current and future safety concerns. The Contractor shall prepare the agenda and meeting minutes for each Safety IPT and deliver them to the TLDHS PMO. The draft meeting agenda shall be delivered NLT 5 business working days prior to the IPT for review and comment. The meeting minutes are due NLT 5 business working days after IPT adjournment. CDRL A001 “ Meeting Agenda CDLR A002 “ Meeting Minutes The Contractor safety SME shall also participate in the TLDHS PMO meetings and other safety related reviews and meetings such as the Test Readiness Reviews, Technical Review Board, Program Management Reviews, Configuration Control Board, and information assurance meetings. The Contractor safety SME shall also be a member of the DF System Engineering and Test and Evaluation IPTs to provide expert technical safety support. CDRL A001 “ Meeting Agenda (contractor format) CDRL A002 “ Meeting Minutes (contractor format) 7.3 Safety Testing The Contractor shall perform independent government safety testing in support of the Government Software Acceptance Testing and other government testing events. The Contractor shall assist in the development of the TLDHS Test and Evaluation Plan, to identify ESOH testing requirements and to verify the effectiveness of the selected test strategy and mitigation measures. The contractor shall document and brief the safety testing process and results to the TLDHS PMO. The Contractor shall observe and participate in the TLDHS PMO test events, contribute to the Government Test Reports and assist with the Test Incident Report data source. Additionally, the Contractor shall develop safety related tests and exercises for the TLDHS PMO to ensure all safety requirements are fully implemented and the system operates safely in its intended environment with trained operators. The Contractor shall also perform the review of the TLDHS systems engineering documents and provide comments to the TLDHS PMO with respect to safety. CDLR A007 - Safety Test Report 7.4 Safety Hazard Analysis The Contractor shall perform safety hazard evaluation and analysis to assess probability of occurrence and severity of consequences on the system itself, and other external systems with which TLDHS interfaces. The Contractor shall propose mitigations for those safety hazards to the TLDHS Prime Developer and PMO. The Contractor shall ensure that all potential safety hazards of TLDHS are fully understood, documented, and presented to the TLDHS PMO for acceptance of residual safety risk. The Safety Assessment Report (SAR) shall be furnished to the TLDHS PMO and updates to the SAR as required. CDRL A008 - Safety Assessment Report 7.5 Safety Hazard Tracking The Contractor shall provide specific controls and precautions needed to eliminate or minimize safety hazards. The hazards and the mitigation measures used to eliminate or minimize them, shall be identified and documented. The Contractor shall maintain and update the Hazard Tracking Record as required to include tracking new and residual hazards, their mitigation measures and closures. CDRL A009 “ Safety Hazard Tracking Report 7.6 Documentation The Contractor shall develop, update, and maintain the SSPP that details the task and activities of system safety management, to identify, evaluate, and eliminate or control safety hazards. The Contractor shall ensure that the TLDHS ESOH risks are analyzed and managed IAW DoD 5000.2. The Contractor shall work with the TLDHS PMO to mitigate and reduce ESOH risks, ensure the system continues to meet all project performance goals and readiness. The PESHE summarize the TLDHS ESOH and will be updated as required. The Contractor shall prepare safety release letters for test events as required. Release letters are prepared using Naval Correspondance format. The Contractor shall assist the development and update of the TLDHS program documents to ensure system safety is accurately covered in system engineering and logistic disciplinary. CDRL A010 “ PESHE CDLR A011 “ Safety Releases 7.7 Software Code Review The Contractor shall inspect portion of the software codes to support the safety testing, safety oversight and assure software code quality is built into TLDHS software products. The contractor shall inspects those areas of the code deemed most critical, or most likely to contain egregious defects, as it determines is appropriate. The software code reviews provide a means of accepting source code into development baselines or handing it off to the next stage of development, such as testing. In addition to utilizing inspections, testing and analysis tools, the Contractor shall review and audit the Prime Developer ™s Software Quality Assurance Plan. The software code review will also validate the build procedures for additional software versions. 7.8 Techncial Review The Contractor shall analyze the TLDHS design (software and hardware) in order to properly understand the architecture to support the safety oversight. The analysis may include monthly scheduled Design Reviews over the telephone, as well as pertinent software documentation reviews. Additionally, other information provided from the Prime Developer such as object models, class interactions, and interface diagrams will be analyzed. The Contractor shall ensure that appropriate levels of quality, reliability, maintainability, and extensibility are built into the TLDHS software, and that approved software development practices and industry-standard œbest practices  are followed. 8.0 GOVERNMENT PROPERTY MANAGEMENT The Contractor shall account for all Government Furnished Property/Government Furnished Equipment/Government Furnished Material (GFP/GFE/GFM)(jointly referred to as œproperty ) to complete the tasks defined herein. The Government will provide the GFP/GFE/GFM directly to the Contractor via Form DD-1149 or equivalent shipping/transfer document. In all circumstances where GFP/GFE/GFM is provided directly, the Contractor will comply with FAR Clause 52.245-1. The Contractor shall account for all Government Property in accordance with the requirements of the FAR and DFARS. The GFE report shall be provided once and as required to the TLDHS PMO. The report shall contain at least the basic information required by FAR Part 45.505-1. These reports may be submitted by electronic media in a format agreed to by the TLDHS PMO. The Contractor shall also present Government Property status at the IPRs and the status shall be incorporated in the IPR meeting minutes. CDRL A012 “ GFE Report 9.0 DELIVERABLES All data deliverable under this SOW shall be in compliance with the format and guidance specified in the DoD 5000.2 series, as applicable, or a specified in the Section 12.0 Contract Data Requirements List (CDRL). All data deliverables shall be provided electronically to the Government Contracting Officer ™s Representative and the identified TLDHS PMO personnel. 10.0 PLACE OF PERFORMANCE The place of performance for this Contract is at the Contractor facility, Marine Corps Systems Command, Quantico VA, and other designated Government and Contractor facilities. 11.0 PERIOD OF PERFORMANCE The overall period of performance for this SOW shall be from date of contract award through X April 2014. 12.0 CDRL The table below outlines the CDRL for this effort. CDRL #CDRL TitleData Item DescriptionDelivery Frequency A001Meeting AgendaContractor FormatAs required A002 Meeting MinutesContractor FormatAs required A003Contractor ™s Progress, Status and Management ReportContractor FormatMonthly A004Contractor ™s WBSContractor FormatOnce and As required A005Trip ReportContractor FormatAs required A006SSPPContractor FormatOnce and As required A007Safety Test Report Contractor FormatAs required A008Safety Assessment ReportContractor FormatAs required A009Safety Hazard Tracking ReportContractor FormatAs Required A010PESHEContractor FormatAs required A011Safety ReleasesNaval CorrespondanceAs required A012GFE ReportContractor FormatOnce and As required
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/USMC/M67854/M6785412I2413/listing.html)
 
Record
SN02629517-W 20111130/111128234207-1d79f9a3b473dbdc1ff74299da68c8b9 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.