Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF JULY 31, 2019 FBO #6459
SPECIAL NOTICE

99 -- Live Virtual Constructive for Training (LVCT)Request for Information

Notice Date

7/29/2019
 

Notice Type

Synopsis
 

NAICS

541330 — Engineering Services
 

Contracting Office

N61340 Naval Air Warfare Center Training Systems Division 12211 Science Drive Orlando, FL
 

ZIP Code

32826
 

Solicitation Number

N6134019R0160
 

Archive Date

8/27/2019
 

Small Business Set-Aside

N/A
 

Description

1 INTRODUCTION 1.1 BACKGROUND The Naval Air Warfare Center Training Systems Division (NAWCTSD) is seeking information from industry regarding capabilities and abilities to provide Live Virtual Constructive Training (LVCT) support. The overarching objective of LVCT is the integration of various training systems and live ranges within an integrated training environment. The complexities involve the coordination of efforts and plans between many centers, sites, platforms, and organizations. Establishing a robust System-of-Systems (SoS) LVCT capability is a massive undertaking that involves the collaboration of multiple stakeholder organizations. 1.2 SCOPE Each of the systems listed in paragraph 1.2 has a separate prime contractor. The government is seeking a contractor to perform: 1) technical management of the LVCT-related SoS requirements, discrepancy/deficiency reports (DR), and modifications of the aforementioned Navy systems/center, 2) data analytics and visualization, 3) cybersecurity support. The anticipated award date is 4QFY21 with deliveries commencing in 4QFY22 and completion in 4QFY24. The contract period of performance will be three years with two additional one-year option periods for a total of 5 years. 1.2.1 Technical Management and Rapid Remediation The prime contractors shall develop the hardware and software modifications needed to remedy identified DRs. The future awardee of this contract shall coordinate the rapid implementation of these modifications to correct the DRs. The interdependency among DRs will require coordinating the installation of updates by different contractors to occur in parallel. The intent of these modifications is to rapidly fix capabilities previously delivered to the Fleet. Programmatic and technical management are required to manage a contract that will include the rapid implementation of DR fixes. The current number of DRs is 85 and growing. The expected duties in regard to the Rapid DR Fixes contract management include: a. creating teaming agreements with platform contractors, b. managing a complex database of requirements and DRs, c. maintaining configuration management database for SoS and its composing systems, d. requesting/evaluating proposals from appropriate platform contractors, e. coordinating integration support, and f. coordinating test and evaluation activities. g. coordinating updates to platform technical documentation h. coordinating logistical support 1.2.2 Data Analytics The Data Analytics work package requires the contractor to analyze and perform data visualization tasks for metrics to include, but not limited to: a. Training Readiness (TR) Levels, Resource Usage, and Trainer Effectiveness Levels, b. program and technical management metrics for the LVCT SOS, c. provide data capture and storage, and d. detect LVCT-related trends and anomalies. 1.2.3 Cybersecurity The contractor shall support Cybersecurity through the optimization of cybersecurity and multi-level security requirements on a cross-platform and joint level. 1.3 PLACE OF PERFORMANCE This effort involves deliveries to the following systems: FA-18/EA-18 training systems, E-2D training systems, H-60 training systems, P-8 training systems, F-35 training systems, Next Generation Threat System (NGTS), and Navy Aviation Distribution Training Center (NADTC) Travel may be required to: NAWCTSD/Naval Support Activity (NSA) Orlando, FL Naval Air Station (NAS) Jacksonville, FL Marine Corps Air Station (MCAS) Beaufort, SC NAS Whidbey, WA NAS Lemoore, CA MCAS Miramar, CA Naval Surface Warfare Center (NSWC) Corona, CA NAS Oceana, VA 2 APPLICABLE DOCUMENTS American National Standards Institute (ANSI)/Electronic Industries Alliance (EIA) ANSI/EIA-649-B 2011 - Configuration Management Standard (Copies of the above document are available from www.ansi.org, http://global.ihs.com/, or Global Engineering Documents, 15 Inverness Way, East Englewood, CO 80112.) ANSI/Institute of Electrical and Electronics Engineers (IEEE) IEEE 29418-2018 - ISO/IEC/IEEE Systems and Software engineering “ Life Cycle processes “ Requirements Engineering IEEE 15289-2019 - ISO/IEC/IEEE Systems and Software Engineering “ Content of Life-Cycle Information Items (Documentation) IEEE 12207-2017 - ISO/IEC/IEEE Systems and Software Engineering “ Software Life Cycle Processes (Copies of this document are available from www.ieee.org or IEEE Service Center, 445 Hoes Lane, Piscataway, NJ 08854-1331.) 3 REQUIREMENTS 3.1 PROGRAM MANAGEMENT The contractor shall organize, coordinate, and control the program activities to ensure compliance with the contract requirements and the timely delivery of the required product and services. The contractor shall provide the necessary program management, systems engineering, design engineering, materials, services, equipment, facilities, testing, technical, logistics, manufacturing, and clerical support for the efforts described in this RFI. The contractor shall measure, monitor, and assess the progress of the work performed and costs incurred under the contract. 3.1.1 Program Planning The purpose of the program planning process is to produce and communicate effective and workable program plans. The contractor shall define, document, manage, and apply program planning processes IAW IEEE Std 12207-2017. 3.1.2 Integrated Product Teams (IPTs) The contractor shall define, document, implement, and maintain an IPT structure for the duration of the contract. The purpose of an IPT is to bring together the functions that have a stake in the performance of a product or process and concurrently make integrated decisions affecting that product or process. IPT membership will consist of multi-functional stakeholders working together with a product-oriented focus. Each IPT will be empowered to make critical life cycle decisions regarding each product or process within their purview. IPTs will be applied at various levels ranging from the overall structure of an organization to informal groups functioning across existing units. With Government input, the contractor shall define and document the composition, structure, roles, and responsibilities of each IPT. Each IPT will maintain a list of membership. Each IPT will consist of Government and contractor personnel and have Government and contractor co-chairs. Each IPT will publish an agenda before each meeting. Each IPT will record and maintain meeting minutes. IPT minutes will be shared among and between the other IPTs. 3.1.3 Technical Management Support The contractor shall provide technical management support to LVCT. The contractor is expected to perform the following work: a. Support budgeting; project planning; program planning; and maintaining program information b. Provide risk assessments and cost analysis to evaluate implementation and affordability. c. Maintain an Integrated Master Plan (IMP) to manage all aspects of the LVCT program. d. Maintain an Integrated Master Schedule (IMS) that illustrates time phasing of the tasks to be accomplished to ensure that the IMP criteria are satisfied and that all events are completed. e. Implement an integrated risk management program to identify and assess cost, schedule and performance risks to the program; implement necessary risk mitigation procedures and report on mitigation progress f. Coordinate required life-cycle support for any software/hardware modifications. 3.1.4 Risk Management The purpose of the risk management process is to continuously identify, analyze, treat, and monitor the risks to the program. The contractor shall conduct risk management to systematically control the uncertainty in the program ™s ability to meet cost, schedule, and performance requirements. The contractor shall provide the Government visibility into the contractor ™s tools, assessment, mitigation, and control techniques. The contractor shall define, document, manage, and apply a risk management process IAW IEEE Std 12207-2017. The contractor shall participate in the Government Risk Working Group established for this program. 3.1.5 In-Process Reviews (IPR) The contractor shall conduct a monthly IPR for each month during the period of performance or until Government acceptance via DD-250 of all CLINs. The Government Program Manager POC identified in the Contract will chair the monthly IPRs. IPRs shall provide attendees with information regarding the status and planned activities of the program. With the exception of the first IPR, all IPRs will be conducted virtually with representatives from the contractor and Government present. IPRs shall include the following: a. A presentation on the status of the overall program b. Team structure and contact list (names, responsibilities, phone numbers, and email addresses) c. Review of procurement status d. Review of the schedule status- to include integration, delivery, installation, and test events e. Review of risks- potential issues with integration, delivery, receipt, or testing of materials 3.2 CONFIGURATION MANAGEMENT (CM) The purpose of the CM process is to establish and maintain the integrity of identified Configuration Items (CIs) over their lifecycle. The contractor shall define, document, manage, and apply a CM process IAW IEEE 12207-2017; and ANSI/EIA-649-B 2011. The contractor shall place Government-Furnished Software (GFS), Non-Developmental Items (NDI), and Commercial Item software, and each item ™s associated documentation under CM upon receipt. The contractor shall place Commercial Item software items under CM as œdisk image  files of the physical media. The contractor shall provide configuration management support to LVCT. The contractor is expected to perform the following work: a. Implement, manage, and maintain a LVCT System Level Configuration Management process for the LVCT Change Configuration Board (CCB). Configuration management services include, but are not limited to, maintaining LVCT system level documents; providing configuration controls to baseline documentation; archiving past baselines and resolving configuration control problems. The CCB obtains and reviews configuration changes, including federate changes, for impacts to LVCT interoperability and LVCT training. b. Coordinate and include the federate changes in the IMS. c. Produce and maintain a Configuration Management Plan for the network configuration including federations. d. Coordinate the assessment of all changes before scheduling the CCB. 3.2.1 Change Management The contractor shall define, document, manage, and apply a process to accomplish change management. The contractor shall use Engineering Change Proposals (ECPs) and Request for Deviations (RFDs) to request changes to an approved baseline. 3.2.2 Configuration Status Accounting The contractor shall define, document, manage, and apply a process to accomplish configuration status accounting. The contractor shall identify and document all items incorporated into or deleted from the training device during development and modification. 3.3 SYSTEMS ENGINEERING The contractor shall use the system engineering processes to define the requirements for the system, to transform the requirements into an effective product, and to verify and validate the functionality of the delivered product. 3.3.1 System Requirements Definition The purpose of the system requirements definition process is to define the requirements for the overarching LVCT SoS and allocate requirements to the appropriate system in a many-to-many relationship. The contractor shall define, document, manage, and apply a requirements definition process IAW IEEE 12207-2017. 3.3.2 System-of-System Discrepancy Report and Requirements Analysis The contractor shall define, document, manage, and apply a SoS analysis process. The contractor shall analyze the interaction between systems, subsystems, and components to determine proper attribution of DRs and requirements to the appropriate platform. The contractor shall define, document, manage, and apply a requirements analysis process IAW IEEE 12207-2017; and IEEE 29418-2018. The contractor shall decompose and derive requirements IAW the criteria within IEEE 29418-2018. The contractor shall record DRs, requirements, technical SOW requirements, and contractor decomposed and derived requirements within the Requirements Traceability/Verification Matrix (RTVM). 3.3.3 Traceability The contractor shall define, document, manage, and apply a process and mechanism to accomplish traceability between the discrepancy reports, requirements, allocated design baseline, implementation configuration items, and test procedures IAW IEEE 15289-2019. The contractor shall utilize an electronic tool (e.g. Doors, RequisitePro, Access Database, and Excel Spreadsheet) to accomplish the requirement traceability function. Traceability shall be bi-directional. Backward traceability shall permit each RTVM element to explicitly trace to a source reference from a previous stage of development. Forward traceability shall permit each RTVM element to explicitly trace to a reference in a later stage of development. The contractor shall provide the Government access to the traceability tool and its database. 3.3.4 System Architectural Design The purpose of the system architectural design process is to identify which system requirements should be allocated to which segments (subsystems) of the system. The contractor shall define, document, manage, and apply a system architectural design process IAW IEEE 12207-2017. The contractor shall place links to the system architectural design in the RTVM to accomplish bi-directional traceability. 3.4 INTEROPERABILITY ENGINEERING SUPPORT The contractor shall provide interoperability engineering support to LVCT. The contractor is expected to perform the following work: a. Review training system Contractors design approach, criteria, and design reports. Evaluate the design approach, criteria and reports, and provide evaluation comments. b. Continuously assess training system Contractor performance and recommend appropriate action when Contractor delinquencies of deficiencies occur. c. Analyze potential requirements for modifications on training systems in the operational phase of the training system life cycle. This involves extensive research and coordination, including direct contact with fleet activities, Government laboratories, and device/system users. d. Evaluate technical proposals and work statements submitted by commercial Contractors or in-house resources. Recommend the best technical approach submitted in response to the specification. Clarify engineering design ambiguities, highlighting areas of design deficiency, and resolving conflicts in the proposed engineering technical approach. Document the configuration, design, and performance characteristics of the proposed training system. e. Support exercises involving LVCT SoS assets, including Technical Assistance Agreements (TAAs) when required, as directed by the government in a task order. f. Provide test program/project support such as scheduling events, program planning, cost, schedule, and performance coordination. g. Support development and review of technical requirements of test planning and reporting efforts. This shall include consideration of test processes and objectives, data acquisition, data reduction and analysis, along with test documentation/test resource requirements development. h. Provide engineering and technical services during pretest, test, and post-test activities. i. Coordinate and support the execution of local and off-site test activities with DOD test sites and other entities including independent evaluators. j. Integrate and update multi-format technical data. 3.5 DATA ANALYTICS The contractor shall provide data analytics support to LVCT. The contractor is expected to perform the following work: a. Generate data analytics plan for LVCT describing the architecture, integration, implementation, and sustainment strategy for the data analytics solution. b. Capture, consolidate and manage data from a variety of sources c. Perform data analysis of metrics such as: TR Levels, Resource Usage, and Trainer Effectiveness Levels d. Provide data storage solution e. Develop software solution with dynamically-updated data dashboard f. Create a data analytics platform that: exports data subsets, generates ad hoc queries and reports, and provides automatic delivery of predefined reports g. Provide administration tools and procedures for the support and maintenance of the proposed solution. 3.6 CYBERSECURITY The contractor shall provide cybersecurity requirements support to LVCT. The contractor is expected to perform the following work: a. Assist the Government with related input on Information Assurance (IA) security requirements to be included in statements of work and other appropriate procurement documents. b. Participate in the development or modification of the computer environment IA security program plans and requirements. c. Develop procedures to ensure system users are aware of their IA responsibilities before granting access to DOD information systems d. Monitor system performance and review for compliance with IA security and privacy requirements within the computer environment. 3.7 SPECIAL REQUIREMENTS The proposed work requires at least a Secret Security clearance. Security clearance shall be obtained prior to reporting on-site for work. The Contractor shall provide personnel who hold a security clearance that meets the security requirements of the program. The contractor is expected to adhere to the following general security policy requirements through the length of the contract: a. Provide OPSEC protection for classified information and sensitive information. b. Adhere to security policy, procedures, and requirements for classified information. c. Safeguard classified information and meet the security requirements identified in the DD Form 254 and enforce these safeguards throughout the life of the contract d. Not process DOD information on public computers (e.g., those available for use by the general public in kiosks or hotel business centers) or computers that do not have access control. e. Protect information by no less than one physical or electronic barrier (e.g., locked container or room, login and password) when not under direct individual control. f. Sanitize media (e.g., overwrite) before external release or disposal. g. Encrypt the information that has been identified as Controlled Unclassified Information (CUI) when it is stored on mobile computing devices such as laptops and personal digital assistants, or removable storage media such as thumb drives and compact disks, using the best available encryption technology. h. Limit information transfer to Sub Contractors or teaming partners with a need to know and a commitment to at least the same level of protection. i. Transmit e-mail, text messages, and similar communications using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and Transport Layer Security (TLS). j. Encrypt organizational wireless connections and use encrypted wireless connection, where available, when traveling. When encrypted wireless is not available, encrypt application files (e.g., spreadsheet and word processing files), using no less than application-provided password protection level encryption. k. Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients. l. Not post DOD information to Web site pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to Web site pages that control access by user identification or password, user certificates, or other technical means and provide protection via use of TLS or other equivalent technologies. Access control may be provided by the intranet (vice the Web site itself or the application it hosts). m. Provide protection against computer network intrusions and data exfiltration, including no less than the following: (1) Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware. (2) Monitoring and control of inbound and outbound network traffic as appropriate (e.g., at the external boundary, sub-networks, individual hosts) including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services. (3) Prompt application of security-relevant software patches, service packs, and hot fixes. n. Comply with other current Federal and DOD information protection and reporting requirements for specified categories of information (e.g., critical program information, Personally Identifiable Information (PII), export controlled information) IAW the requirements of the contract. 3.8 ELIGIBILITY NAICS: 541330 Engineering Services PSC: R425 Support-Professional: Engineering/Technical 3.9 SUBMISSION DETAILS Responses to this notice should include key corporate information as well as a brief synopsis of the Contractors experience in providing services specifically as it relates to the capabilities described in this RFI. Your response should provide the following information: a. Your office location b. CAGE Code c. Whether your firm currently has a DCAA approved accounting system d. Point of Contact name, phone number, and email e. Description of your firm ™s past experience and capability to accomplish the tasks and work defined in this RFI. f. Rough order of magnitude for work defined in this RFI. g. The contract numbers and task order numbers of past contracts that represent your firm ™s experience with the types of work described this RFI. h. Your firm ™s past experience and capability to work with classified material up through and including Secret. If you do not have experience on requirements through the Secret classification, your response should clearly state that, and describe what security level your company has experience with. Responses should be provided in a Word document, not to exceed 5 pages, to the Contract Specialist for this solicitation, fernando.cerpa@navy.mil, by 5:00 P.M. on 08/27/2019. Use 12 point Times New Roman font. NAWCTSD is using this notice for the purpose of determining market interest, availability, and adequacy of potential business sources prior to establishing the method of services acquisition and issuance of a request for proposals. Your responses in any form are not offers. Issuance of this request for information notice does not obligate the Government in any way to issue a solicitation or to award a contract in furtherance of the objectives discussed herein. No funds are available to pay for preparing responses to this notice. The Government reserves the right to review and use data at its own discretion. NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (29-JUL-2019); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT 877-472-3779 or fbo.support@gsa.gov REGARDING THIS ISSUE.
 

Web Link

Link To Document
(https://www.fbo.gov/spg/DON/NAVAIR/N61339/N6134019R0160/listing.html)
 

Record

SN05384496-F 20190731/190729230032 (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 |