Attachment 4 Requirements Traceability Matrix.xlsx

XLSX spreadsheet 33 KB Posted Nov 22, 2023

Attached to: Solicitation Notice for Proliferated Low Earth Orbit (PLEO) Satellite-Based Services
Solicitation number: HC101324R0001
Issued by: Defense Information Systems Agency

About this file

Written by GovTribe AI · Dec 21, 2023

This document is a requirements traceability matrix for a solicitation seeking proliferated low Earth orbit satellite-based services. The Defense Information Systems Agency is soliciting proposals to provide operational packaged PLEO services including various managed service offerings that mirror commercial capabilities. Services must meet defined performance requirements for availability, coverage areas, reporting, user terminals, and backhaul. Offerors must provide documentation on partnerships, regulatory approvals, system architectures, and information assurance plans. The contract will have a base period of performance with option periods exercising additional requirements. Services must begin within set timeframes of the award and incorporate service level agreements defining metrics. The selected contractor will report usage and incident data, provide help desk and training support, and receive task orders to activate specific services.

View the file

Other files

File	Type	Posted
Attachment 2 Questions and Answer_20240529.xlsx	XLSX spreadsheet	May 29, 2024
Attachment 2 Questions and Answer_20240503.xlsx	XLSX spreadsheet	May 6, 2024
Attachment 2 Questions and Answer_20240422.xlsx	XLSX spreadsheet	Apr 23, 2024
Attachment 3 Pricing Spreadsheet Template AMD 02.xlsx	XLSX spreadsheet	Apr 17, 2024
RFP - HC101324R0001AMD0002.pdf	PDF	Apr 17, 2024
Attachment 2 Questions and Answer_20240417.xlsx	XLSX spreadsheet	Apr 17, 2024
Questions and Answer_01_20240226.xlsx	XLSX spreadsheet	Feb 26, 2024
240-110-44 Supply Chain Risk Management (SCRM).pdf	PDF	Feb 7, 2024
Attachment 2 Questions and Answer_01_20240206.xlsx	XLSX spreadsheet	Feb 7, 2024
RFP - HC101324R0001AMD0001pdf.pdf	PDF	Dec 15, 2023
Attachment 2 Questions and Answer_20231215.xlsx	XLSX spreadsheet	Dec 15, 2023
Attachment 2 Questions and Answer Template.xlsx	XLSX spreadsheet	Nov 22, 2023
Attachment 8 Nondisclosure Agreement - NDA.pdf	PDF	Nov 22, 2023
RFP - HC101324R0001.pdf	PDF	Nov 22, 2023
Attachment 7 Subcontracting Plan Checklist.docx	DOCX document	Nov 22, 2023
Attachment 1 DD254.pdf	PDF	Nov 22, 2023
Attachment 5 SLA Template.docx	DOCX document	Nov 22, 2023
Attachment 10 Assumptions and Deviations.docx	DOCX document	Nov 22, 2023
Attachment 6 QASP.docx	DOCX document	Nov 22, 2023
Attachment 9 COMSATCOM Information Assurance Questionnaire (CIAQ) Template.xlsx	XLSX spreadsheet	Nov 22, 2023
Attachment 3 Pricing Spreadsheet Template.xlsx	XLSX spreadsheet	Nov 22, 2023

Show all 21

On GovTribe

Work with this file

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

PLEO RTM

Attachment 4
PLEO Requirements Traceability Matrix
PWS Reference	Requirement	Proposal Reference, Volume, Document and Page #	Comments
4	The contractor shall define any partnerships that are required to provide end-to-end service under this contract as well as the management process in place to manage these partnerships.
6	The contractor shall furnish a copy of the valid, current Federal Communication Commission or other applicable regulatory filings for all PLEO constellations and services provided prior to offering services under this PWS.
6.1	The contractor shall provide operational packaged PLEO services.
6.1	This service shall consist of various service offerings provided as end-to-end managed services that mirror the contractor’s commercial offerings.
6.1	Each service provided under this task shall be governed by an SLA that specifies pertinent threshold and objective performance parameters of the service to which the contractor shall commit.
6.1	Proposed operational packaged PLEO services not available at the time of initial contract award, shall be available from the contractor within 36 months of contract award.
6.2	The service provided under this section shall conform to the requirements stated in the TO for the operational customer specific services.
6.2	Operational customer specific PLEO services shall meet the performance requirements stated in section 7.2 below as well as any additional or modified requirements specified in the TO.
6.2	Operational customer specific PLEO services shall be deemed acceptable for DoD missions prior to award of a task order for those services.
6.3	If offered on a task order, the contractor shall provide trial or demonstration capabilities and capacity to the Government prior to the commercial operational capability of the host constellation.
6.3	This service shall be used exclusively for evaluation purposes and shall not support mission or mission critical functions at any time.
6.3	Each service provided under a TO in this task shall be governed by a SLA that specifies pertinent threshold and objective performance parameters of the service to which the contractor shall commit.
6.3	Initial, limited use PLEO services shall be available for activation within 12 months of contract award.
6.4	If compatible equipment is required to utilize the service, the contractor shall ensure the availability of such equipment for purchase or lease by the Government.
6.4.1	The contractor shall provide the equipment based on task order requirements.
6.4.2	Equipment shipment shall be per the requirements of PWS Section 6.4.2.
6.4.3	Equipment warranties shall be per the requirements pf PWS Section 6.4.3.
6.5.1	The contractor shall provide, within 30 days of contract award under the initial TO, system architecture briefings, explanations, and diagrams regarding the inner workings of the system in support of the Government’s requirements and requests as part of the initial minimum order.
6.5.1	This information may be considered proprietary by the contractor and proprietary information shall only be used to address specific Government questions and concerns generally related to system and service operations, security, vulnerabilities, functions, performance, supply chain including key partnerships, and similar attributes of the supplied services and corresponding infrastructure.
6.5.1	The contractor shall conduct technical briefings regarding the system architecture as requested by the Program Management Office (PMO) or contracting activity.
6.5.2	Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall collect and deliver near real-time usage, monitoring, fault/incident/outage reporting, and information access to ensure effective and efficient operations, performance, and availability consistent with commercial best practice.
6.5.2	Total delay objective in network operations information availability, as measured from incident detection to incident reporting, shall be 30 seconds or less; threshold reporting delay shall match commercial operation best practice.
6.5.2	The contractor’s NetOps monitoring capability shall address the following metrics at a minimum: current and past usage reporting, system/network outages (space, ground, transport, operations, etc.), fault reporting, and user terminal status (for all supplied under this PWS in each contractor provided PLEO network).
6.5.2	As part of any commercial service offering furnished under this PWS, the contractor shall provide an online account management tool capability accessible by the Government to report service usage, both aggregated and for each user account, and to manage users' access to services and capabilities.
6.5.2	Usage information shall be updated at a minimum daily.
6.5.2	Usage information shall indicate the time period to which the data is related.
6.5.2	PLEO users shall be able to see monthly and cumulative information.
6.5.2	The contractor’s account management solution shall allow a PLEO service user to query their usage data over a user-specified period.
6.5.2	It shall also allow Government service managers to enable and disable an individual user's service as well as to change user subscription options such as billing group or other service-specific options.
6.5.2	The account management tool shall support a user access hierarchy per industry best practices, which limits access to information and controls as defined for each user.
6.5.2	At a minimum, users shall have the ability to access the fields listed in Table 6-2 from the contractor’s usage database, or their equivalent as appropriate to the contractor’s technology and service type:
6.5.3	Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall perform and report service availability measurements.
6.5.3	Final system availability metrics used for reporting service availability against this contract and the methods for collecting and reporting them shall be by mutual agreement of the parties and shall include all downtime observations used to calculate system availability as required in Table 7-2.
6.5.4	Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall report the status of all service activations by the 5th business day of each month.
6.5.4	For each service account identified in the service activation plan, the monthly status report shall document the service activation date, new service account information, service authorization information, and the type of service provided, significant issues and any other salient information as established in the service activation plan.
6.5.5	Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall deliver a MSR to the COR, KO, Contract Specialist (CS), and the Regional Satellite Support Center (RSSC)-West.
6.5.5	MSR is due by the 5th business day of each month and shall cover information from the previous month.
6.5.5	The MSR contents shall be by mutual agreement of the parties as documented in relevant Task Orders but shall include at a minimum:
	• Top ten risks and associated mitigation plans
	• Service activation status
	• Troubleshooting and customer assistance provided
	• Usage and fault reporting process updates
	• Host nation agreement (HNA), Licensing, and related issues (if required)
	• Planned Changes
	• Availability of all items on the PLEO Equipment List (if applicable)
6.5.5	A summary of expedited/emergency activation of subscriptions and terminals in Government possession shall be included in the MSR.
6.5.5	The contractor shall confirm that all personnel, to include any new personnel on the contract, have executed the DISA-provided NDA and the NDA is current as of the date of the MSR.
6.5.5	The contractor shall confirm that all personnel, to include any new personnel on the contract, have executed the DISA-provided NonDisclosure Agreement (NDA) (Attachment 8) and the NDA is current as of the date of the MSR.
6.5.5	MSRs shall be sent to the KOs and CORs.
6.5.6	Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall provide a quarterly usage report containing the fields specified in Table 6-2 above for all PLEO services.
6.5.6	Microsoft Excel formatted reports shall be submitted on the 5th business day of January, April, July, and October for the preceding quarter.
6.5.7	Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall provide automated, verbal and written status reports to the RSSC-West, COR, and other designated POCs in accordance with timelines, formats, protocols, and escalation procedures to be agreed by the parties and documented in the Communications and Escalation Plan outlined in paragraph 6.6.5 to be submitted 30 calendar days following base contract award.
6.5.7	In the event of a service outage, the contractor shall provide verbal and written status reports to the RSSC-West, COR, and other designated POCs in accordance with timelines, formats, protocols, and escalation procedures to be agreed by the parties and documented in the Communications and Escalation Plan.
6.5.8	The contractor shall maintain compliance with applicable IA policies as defied in the COMSATCOM Information Assurance Questionnaire (CIAQ).
6.5.8	Tthe contractor shall submit, on the 5th calendar day of each month, an IA monthly report deliverable to the COR.
6.5.8	The contractor shall provide their IA/Incident Reporting process 30 calendar days following contract award.
6.5.9	Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall provide weekly updates (during normal business hours) to the COR on the current status of all in-process task orders (task orders that have not been delivered) in order to ensure that current equipment order information is available.
6.5.9	Weekly updates shall include (at a minimum): task order number, task order customer point of contact (POC), equipment type/model, quantities, shipment date, and warranty start and end dates.
6.5.9	The weekly updates shall be provided per the deliverables schedule and shall include data for the previous week.
6.5.9	Availability of all items on the PLEO equipment list shall be included in the monthly status report (MSR).
6.6.1	Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall, included as part of said services, English speaking technicians 24x7 help desk technical support for the contractor’s services and equipment as well as government-specific capabilities provided by the contractor, if any, in accordance with a communication and escalation procedures to be agreed by the parties and documented in the Communications and Escalation Plan.
6.6.1	Access to the help desk shall be made available by phone, e-mail, chat, text, video call and remote access to user devices as required by the specifics of the situation.
6.6.1	Help desk support shall cover Tier 1- basic help desk resolution, Tier 2 – in-depth technical support and Tier 3 – expert technical support.
6.6.1	Resolution times for Tier 1, Tier 2 and Tier 3 support shall be within 1 calendar day, 2 calendar days and 7 calendar days of initial help desk contact respectively.
6.6.1	Customer service support to handle billing questions, contract related inquiries, and any online account management tool queries shall be available, at a minimum, Monday through Friday 7:00 a.m. to 5:00 p.m. eastern time, excluding United States Government holidays.
6.6.1	The contractor shall provide field service representatives to support initial installation, configuration, and activation tasks, as well as ongoing operations and maintenance activities as necessary to maintain equipment and service access.
6.6.1	Field service support shall be available on an annual and ad-hoc daily basis if required. FSR support will be addressed as required at the TO level.
6.6.2	1. Prior to incurring any long-distance travel expenses, the contractor shall obtain written approval from the COR approving the travel dates, expected duration, origin and destination, purpose, estimated costs, and the number and names of personnel traveling.
6.6.2	2. Travel Authorization Requests shall be completed and pre-approved by the government COR.
6.6.2	3. All travel associated with this contract shall be in accordance with FAR 31.205-46. The COR will certify invoices prior to processing for payment.
6.6.2	4. Local travel shall not be reimbursed, unless otherwise specified in the applicable task order.
6.6.2	5. The contractor shall provide a trip report with supporting documentation to the COR within 5 business days of completion of travel detailing the work completed.
6.6.2	6. For service calls requiring contractor travel to a remote location inaccessible through commercial air transportation, the contractor shall work with the COR (or other DoD office if stipulated in the TO) to arrange provision of DoD travel to the remote site.
6.6.3	The contractor shall provide training needed to use the contracted service under each TO.
6.6.3	The contractor shall provide an initial training session of the online account management tool (presentation method to be agreed upon in the TO) and any equipment and services purchased as part of the TO to both CSCO and DoD representatives within 15 calendar days of the start of the first operational service provided on the task order.
6.6.3	Training materials or soft copies of instructions shall be provided to users as they obtain services.
6.6.4	Not more than 30 calendar days following base contract award, the contractor shall present a written SAP to the Government, detailing the contractor’s approach to providing service activation.
6.6.4	The SAP shall outline the steps required to activate service including a timeline from receipt of TO to successful service activation.
6.6.5	The contractor shall provide a Communications and Escalation Plan including, at a minimum, the contractor’s proposed communications and escalation procedures relative to faults (refer to section 6.5.7), service interruptions, anomalies EMI/RFI incidents, customer service and support (refer to section 6.6.1) and other items that could negatively impact any aspect of the user experience associated with service provided.
6.6.5	The plan shall include at a minimum the contractor’s proposed timelines, formats and protocols for communications and escalation and shall be submitted 30 calendar days following base contract award and shall be mutually agreed upon between the Contractor and the Government.
6.6.5	The plan shall be updated as required based on the mutual agreement of the parties.
6.6.6	To suspend service, service representatives, CSCO, or customers who are granted authority will notify the contractor requesting suspension of services on the specified subscription or terminal. The contractor shall notify the service provider/value added reseller and end user of the date of suspension, thus restricting all access.
6.6.7	While any TO is under contract, the contractor shall provide EMI/RFI identification, characterization, geo-location, and resolution in accordance with protocols and escalation procedures to be agreed by the parties in the Communications and Escalation Plan outlined in paragraph 6.6.5.
6.6.8	The contractor is responsible for and shall secure all local, national and international approvals and licenses to operate and provide services provided under this PWS including but not limited to HNAs, host nation approvals, landing rights, operating agreements, site licenses, frequency clearances, and international approvals for radio spectrum operations for DoD to access the entire contractor service coverage area.
6.6.8	Frequency clearances and approvals for coverage areas proposed shall be available prior to contract award. Note: This applies for services contracted for at either the IDIQ or TO level.
6.6.9	Not more than 30 calendar days following base contract award, the contractor shall provide a completed COMSATCOM Information Assurance Questionnaire (CIAQ) that details the contractor solution IA security posture.
6.6.9	Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall continually monitor and verify IA is in compliance with the contractor’s security posture as documented in the CIAQ.
6.6.9	IA incident notification shall be made within 24 hours; detailed incident report is provided within 5 business days.
6.6.9	Reports shall be submitted in a Microsoft Word (.doc) or .PDF file format that provides a written summary of events/changes for the reporting period.
6.6.10	The contractor shall provide within 30 calendar days of base contract award a service management plan that details the approach the contractor will use to manage all of the aspects of service delivery.
6.6.10	The plan shall include documents, policies, procedures, briefings, explanations, and diagrams regarding the approach taken to manage the offered services in support of the Government’s requirements and requests.
6.6.10	This information shall system and service operations, security, vulnerabilities, functions, performance, supply chain including key partnerships, and similar attributes of the supplied services and corresponding infrastructure.
6.6.10	The contractor shall conduct technical briefings regarding the service management plan as requested by the PMO or Contracting Activity.
7.1	The contractor shall provide operational PLEO service as listed section 6.2 that meets the following performance requirements:
	• Access to a sufficient number of active satellites involved in providing operational service in one or more geographic region(s) of coverage. Geographic regions of coverage shall be defined by the contractor.
	• Reporting capability to facilitate accurate accounting for services provided.
	• User terminals, if necessary, to allow for operational use of the contracted service.
	• Gateway/backhaul capability sufficient to transport data between terminals and the commercial internet, or products between the contractor's system and users via the commercial internet.
7.1	For each activated user, the contractor shall provide operational PLEO service that satisfies the threshold performance requirements for the parameters identified in Table 7-1 below and as agreed upon via a SLA. Additional service-specific parameters may be defined and required in a TO, such as packet latency and data rates for a communication service.
7.1.1	The contractor shall provide low-latency PLEO service and capabilities to all domains and use cases in accordance with performance parameters as specified above and in SLAs corresponding to service offerings.
7.1.1	If user terminals are a feature of the service, both fixed-position and mobile users shall be supported.
7.1.1	The contractor shall provide terrestrial connections for PLEO service from the PLEO ground station(s) or portal(s) serving each user to the endpoint(s) identified on the task order, if so specified.
7.1.1	The contractor shall provide service in an area of geographic coverage (the “coverage area”) that shall be the same or greater than that provided to all of the contractor’s customers (an area that covers the sum of all service coverage areas offered to all of the contractor’s customers).
7.1.1	The contractor shall provide service invoices based upon service usage (messages, packets, megabytes, products, effects, as appropriate) consumed or per subscription in accordance with contractual instructions on the TO.
7.1.2	The contractor shall provide a service priority option that the Government may at its discretion purchase and activate on a subscription-by-subscription basis (that is, per user).
7.1.2	When this option is enabled for a subscription, the service for that subscription shall operate at a priority level superior to all other user service priorities within the contractor’s service except, where applicable, those for users associated with assuring “safety of life” services as mandated by International Regulations (e. g. Global Maritime Distress and Safety Services).
7.1.3	The contractor shall support expedited/emergency (e.g., a war started) activation service and associated terminal units in the Government inventory. “Government Inventory” is understood to mean inventory in the possession of the United States Government and not Government furnished property (GFP) provided to the contractor.
7.1.3	The contractor shall support such requests only under the direction of the KO. The expedited/emergency activation will be followed with a written/electronic TO.
7.1.4	The contractor shall provide provisioning services for PLEO satellite-based services on a contractor type approved user terminal if one is required for the service to function
7.1.5	The contractor shall provide terrestrial interconnect to the Internet for access to their business systems, through which users may request products or effects, receive products or effect confirmations, or route traffic to/from any Internet-accessible address including Government network entry points.
7.1.5	In addition, if specified in a TO, the contractor shall support Government-developed solutions to provide users of PLEO services with reach-back connectivity into the DoD information network and services such as the non-classified internet protocol router network, secret internet protocol router network, defense information system network, federal risk and authorization management program certified cloud services, and others.
7.1.5	In order to accommodate these services, the contractor shall ensure the capability of a terrestrial connection into the PLEO network.
7.1.5	The contractor shall ensure that Government furnished routers may be hosted where terrestrial access to the PLEO network is available.
7.1.5	Traffic shall be identified by secondary APN(s), VLAN(s), network slices, or equivalent, or by designated static addresses, to ensure access to hosted routers. In this case the Government will provide routers to the contractor for installation. Deliverables are listed in Table 7-4 below.
7.2	The contractor shall provide initial, limited use PLEO service as listed in 6.3 that meets the following performance requirements:
	• Access to a sufficient number of active satellites involved in providing limited-service coverage in one or more geographic region(s) of coverage. Geographic Coverage area shall be based upon government requirements within the current capabilities of the satellite coverage and licensing.
	• Reporting capability to facilitate accurate accounting for services provided.
	• User terminals, if necessary, to allow for limited, trial use of the contracted service.
	• Gateway/backhaul capability sufficient to transport data between terminals and the commercial internet, or products between the contractor's system and users via the commercial internet
7.2	For each activated user, the contractor shall provide initial limited use PLEO service that satisfies the performance requirements identified in Table 7-2 below and as agreed via a SLA.
10	If working at the Contractor’s facility, the Contractor shall prepare all deliverables and other Contract documentation utilizing Contractor resources.
10	The primary places of performance shall be determined in each individual TO.
12.2	All personnel performing on or supporting a DISA contract in any way shall be United States citizens.
12.3	All personnel requiring Top Secret and SCI access under this contract shall undergo a favorably adjudicated Tier 5 (T5) investigation (formerly known as a Single Scope Background as a minimum requirement.
12.3	All personnel requiring Secret access under this contract/order shall undergo a favorably adjudicated Tier 3 (T3) Investigation formerly known as a National Agency Check, Local Agency Check and Credit Check or Access National Agency Check and Inquiries as a minimum investigation.
12.4	Visit requests shall be processed and verified through the Defense Information System for Security (DISS)or Defense Information Security System (DISS) as appropriate to SMO DKABAA10 and SMO DKADAL.
12.6.1	Contractor personnel shall comply with all local security requirements including entry and exit control for personnel and property at the government facility.
12.6.2	Contractor employees shall be required to comply with all Government security regulations and requirements.
12.6.2	Failure to comply with Government security regulations and requirements shall require the company to provide the Government with a written remediation/corrective action plan; furthermore, failure to comply with such requirements can be cause for removal and the contractor will not be able to provide service on this contract.
12.6.4	The Contractor shall not divulge any information, classified or unclassified, about DoD files, data processing activities or functions, user identifications, passwords, or any other knowledge that may be gained, to anyone who is not authorized to have access to such information.
12.6.4	The Contractor shall observe and comply with the security provisions in effect at the DoD facility.
12.6.4	Identification shall be worn and displayed as required.
12.6.6	All contractor deliverables shall be marked in accordance with DoDM 5200.01, Vol. 3, DoD Information Security Program: Protection of Classified Information; DoDI 5200.48, Controlled Unclassified Information (CUI); and DoDM 5400.07, Freedom of Information Act Program, unless otherwise directed by the Government.
12.6.6	The contractor shall comply with the provisions of the DoD Industrial Security Manual for handling classified material and producing deliverables.
12.6.6	The contractor shall comply with DISA Instruction 630-230-19, Cybersecurity.
12.6.6	The contractor shall afford the Government access to the contractor’s facilities, installations, operations, documentation, databases and personnel used in performance of the contract.
12.6.6	Access shall be provided to the extent required to carry out a program of IT inspection (to include vulnerability testing), investigation and audit to safeguard against threats and hazards to the integrity, availability and confidentiality of data or to the function of information technology systems operated on behalf of CSCO or DoD, and to preserve evidence of computer crime.
14.b	Identification of Potential Conflicts of Interest. In accordance with FAR Subpart 9.5, contractor shall specifically identify, whether or not any potential or actual organizational and consultant conflicts of interest exists at any time during the period of performance of this effort.
14.c	The contractor shall confirm that all personnel, to include any new personnel on the contract, have executed the DISA-provided NDA and the NDA is current as of the date of the MSR.
14.h	The contractor(s) are to summarize any significant supply chain risks as part of their technical volume. The contractor shall submit a SCRM plan as part of the initial task order is awarded a contract that describes how the contractor will reduce and mitigate Supply Chain Risk using the security controls outlined below (further described in CNSSI 1253, Appendix D and NIST SP 800-53), as applicable to your contract.
14.h	The contractor shall provide an updated SCRM Plan to the COR and Program Manager within five business days whenever there is a change that affects one or more security controls as described in the CNSSI 1253 Appendix D (companion publication to NIST SP).

&"-,Bold"Attachment 6 PLEO Requirements Traceability Matrix

File details come from the government source that posted it. Updated Nov 22, 2023.