HC1021-16-T-1034.v0.pdf
PDF 354 KB Posted
- Solicitation number
- HC1021-16-T-1034
- Issued by
-
Defense Information Systems Agency
About this file
Not Listed
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
IQO INQUIRY
FM: PL511
TO: Contractors
DATE (MM/DD/YYYY): 3/14/2016
SUBJECT: HC1021-16-T-1034
A. TYPE ACTION: REAWARD
1. PURPOSE: START A 2.048MB TRANSPARENT, UNSTRUCTURED CIRCUIT
BETWEEN JAATTAA, NORWAY NM1 (NODE 194) AND MILDENHALL, UNITED KINGDOM
NM1 (NODE 180). [THIS IS A REAWARD OF ALLA 262918].
EVALUATION: AFTER RECEIPT OF QUOTES, THE GOVERNMENT WILL FIRST
EVALUATE THE LOWEST PRICE QUOTE. IF THE LOWEST PRICE QUOTE IS
DETERMINED TO BE TECHNICALLY ACCEPTABLE AND OTHERWISE PROPERLY
AWARDABLE, NO FURTHER EVALUATIONS WILL BE CONDUCTED, AND AWARD WILL BE
MADE. IF HOWEVER, THE LOWEST PRICE QUOTE IS DETERMINED TO BE
TECHNICALLY UNACCEPTABLE AND/OR OTHERWISE NOT PROPERLY AWARDABLE, THE
NEXT LOWEST PRICE QUOTE WILL BE EVALUATED UNTIL A QUOTE IS DEEMED
TECHNICALLY ACCEPTABLE AND OTHERWISE PROPERLY AWARDABLE.
QUESTIONS SHOULD BE ADDRESSED TO AISHA.N.VINTES.CIV@MAIL.MIL AND
DISA.STUTTGART.DITCO.MBX.PL511@MAIL.MIL. PLEASE PROVIDE ANY QUESTIONS
IN WRITING NO LATER THAN 28 MARCH 2016 AT 1400 CENTRAL EUROPEAN TIME.
THE GOVERNMENT RESERVES THE RIGHT TO NOT ANSWER QUESTIONS SUBMITTED
AFTER THIS TIME.
SEND QUOTES TO AISHA.N.VINTES.CIV@MAIL.MIL AND
DISA.STUTTGART.DITCO.MBX.PL511@MAIL.MIL.
REQUEST OFFERORS TO PROVIDE THE CAGE CODE AND DUNS NUMBER IN THE
QUOTE.
If there are more than two locations, their information will be found in Attachment B to this Order.
B. ALLA NUMBER: 262918
C. TSP AUTHORIZATION CODE/RESTORATION CODE: STANDARD/R3
D. DEMANDER'S CODE: 251600
E. SERVICE DATE (MM/DD/YYYY): 7/11/2016
F. TYPE OF CIRCUIT:
1. BANDWIDTH/DATA RATE: 2.048 Megabits Per Second
BF26FEB166040
2. SIGNALING MODE: NO SIGNALING
G. LOCATION OF TERMINATION A:
1. ADDRESS: GAMLE EIKESETVEIEN 29; BLDG 334032 STAVANGER, NORWAY
2. ROOM: U13; 1 FL
H. LOCAL PART A:
1. EXTENSION OF TELECOMMUNICATIONS SERVICE: All facilities between vendor's commercial communications interface point and termination location shall be provided by vendor. All cables shall be run in accordance with local site standards
2. INTERFACE: CCITT G.703 AT 2.048MB STANDARD; AS REQUIRED
3. DEMARK: SEE ADDRESS ABOVE.
4. NPA/NXX:
5. UNIQUE INSTALLATION FACTORS: THE COMMERCIAL CARRIER WILL DELIVER
THE LEASED CIRCUIT TO THE COMMERCIAL DEMARC. THE LOCAL COMM UNIT WILL
ASSIST WITH INSTALLATION AS REQUIRED.
6. INSIDE WIRE INSTALLATION/MAINTENANCE REQUIRED: CPIWI-NO/CPIWM-NO
7. CONTACT: (PMRY POC) TCF CIRCUIT ACTIONS;
(UNCLASS ORG) 426.ABS.SC@US.AF.MIL;
(CMCL) 001-475-195-0502; (DSN) 314-224-0502
I. TERMINATION EQUIPMENT A: CABLE CROSS CONNECT; TERM: 4W; COMMERCIAL
VENDOR PROVIDED DSU/CSU
J. LOCATION OF TERMINATION B:
1. ADDRESS: RAF MILDENHALL; BURY STBLDG 591 RM 30AEDMUNDS; SUFFOLK,
IP28-8NF
2. ROOM: 30A; 1 FL
K. LOCAL PART B:
1. EXTENSION OF TELECOMMUNICATIONS SERVICE: All facilities between vendor's commercial communications interface point and termination location shall be provided by vendor. All cables shall be run in accordance with local site standards
2. INTERFACE: CCITT G.703 AT 2.048MB STANDARD; AS REQUIRED
3. DEMARK: SEE ADDRESS ABOVE.
4. NPA/NXX:
5. UNIQUE INSTALLATION FACTORS: THE COMMERCIAL CARRIER WILL DELIVER
THE LEASED CIRCUIT TO THE COMMERCIAL DEMARC. THE LOCAL COMM UNIT WILL
ASSIST WITH INSTALLATION AS REQUIRED.
6. INSIDE WIRE INSTALLATION/MAINTENANCE REQUIRED: CPIWI-NO/CPIWM-NO
7. CONTACT: (PMRY POC) CIRCUIT ACTIONS;
(UNCLASS ORG) 100CS.SCOICIRACT@US.AF.MIL;
(UNCLASS USER) 100CS.100CSITTTECHCONTROL@US.AF.MIL;
(CMCL) 44-1638-238-2090;(DSN) 314-238-2090
L. TERMINATION EQUIPMENT B: CABLE CROSS CONNECT; TERM: 4W; COMMERCIAL
VENDOR PROVIDED DSU/CSU
M. ADDITIONAL INFORMATION:
1. DITCO CSA NUMBER:
2. BASIC AGREEMENT NUMBER: TBD
3. TSR NUMBER: BF26FEB166040
4. CCSD: DIU2M1TT
5. DIVERSITY REQUIREMENTS: N/A
6. LOCATIONS TO BE AVOIDED: N/A
7. TRANSMISSION MEDIA TO BE AVOIDED: N/A
8. NETWORKS TO BE AVOIDED: N/A
9. CIRCUIT PARAMETERS: SEE ATTACHED "CIRCUIT PARAMETERS"
10. TESTING REQUIREMENTS: SEE ATTACHED "TESTING REQUIREMENTS"
11. GOVERNMENT ACCEPTANCE ACTIVITY: TECH CONTROL/D314-238-
2090,C0044-1638-54
12. SECURITY/ REQUIREMENTS: (SP A) ESCORT REQUIRED (SP B) ESCORT
REQUIRED
13. SITE ACCESS REQUIREMENTS: TP SHALL NOTIFY CUSTOMER POC 72 HOURS
PRIOR TO REQUIRING SITE ACCESS.
14. DITCO STANDARD PROVISIONS: Incorporated in full text below
V. QUOTE DUE DATE AND TIME (MM/DD/YYYY): 4/13/2016 4:00 PM
Europe/Berlin
Z. DITCO CONTACT:
Aisha Vintes
DSN: 314-430-2409
aisha.n.vintes.civ@mail.mil
Erica Potthast
DITCO Contracting Officer +(49) (0) 711-680-2887 erica.g.potthast.civ@mail.mil
Standard Provisions
STANDARD PROVISION - 01 - DITCO BASIC AGREEMENT - AUG 2015
To be eligible to receive any Order or Circuit Demand resulting from this Inquiry, Contractor/Telecommunication Provider
(TP) shall have a current DITCO Basic Agreement (BA). DITCO BA contains additional terms and conditions that shall be incorporated into any Order or Circuit Demand by reference. Contractor/TP shall identify its DITCO BA number (i.e., HC10XX-XX-H-XXXX) and agreement date in its quote. Contractors/TPs that do not have a current DITCO BA must obtain a blank BA from the Integrated Defense Enterprise Acquisition System (IDEAS) Contractor web site under references tab https://depsland.csd.disa.mil/html/vendor.html; complete, sign, and return BA to the following applicable email address before submitting a quote. Any questions concerning the DITCO U.S. BA may be emailed to disa.scott.ditco.mbx.basic-agreements@mail.mil, any questions concerning the DITCO Europe BA may be emailed to disa.stuttgart.ditco.mbx.pl511@mail.mil, and any questions concerning the DITCO SWA BA may be emailed to disa.stuttgart.ditco.mbx.pl52@mail.mil.
ACCEPTABLE CONTRACTOR/TELECOMMUNICATIONS PROVIDER (TP) RESPONSE: “UNDERSTAND,” and provide the Contractor/TP’s current BA number and execution date or a new completed and signed BA for execution.
STANDARD PROVISION - 02 - CONTRACTOR/TELECOMMUNICATIONS PROVIDER
ACKNOWLEDGEMENT - AUG 2015
Contractor/Telecommunications Provider (TP) acknowledges it has read and understands the current published version of the
“Acquisition Deskbook Inquiry/Quote/Order” available from the Integrated Defense Enterprise Acquisition System (IDEAS)
Contractor web site https://depsland.csd.disa.mil/html/vendor/vendorreference.html.
ACCEPTABLE CONTRACTOR/TELECOMMUNICATIONS PROVIDER (TP) RESPONSE: “UNDERSTAND.”
STANDARD PROVISION - 04 - QUOTE PREPARATION - AUG 2015
Contractor/Telecommunications Provider (TP) shall identify their legal business name, basic agreement number, DUNS number and CAGE code on all quotes submitted for consideration. Contractor/ TP quote shall respond to each paragraph of this Inquiry separately and to each subparagraph under section M (additional information) separately if applicable.
Contractor/TP shall agree to satisfy all technical aspects of Inquiry. Any technical aspects of Inquiry that Contractor/TP is unable or unwilling to satisfy shall be addressed by Contractor/TP. Contractor/TP shall indicate whether it can meet service date identified in Inquiry. If Contractor/TP cannot meet service date, Contractor/TP shall indicate date that it can provide service. If Contractor/TP’s ability to meet a requested date is dependent upon receipt of an Order or Circuit Demand by a certain date, this condition shall be stated in quote. Contractor’s/TP’s quote shall contain the applicable NPA/NXX for each service location and all applicable charges for service (e.g., charges from subcontractors or other Contractors/TPs, taxes, surcharges, universal service fund, fees, etc.). All charges shall be itemized, with quantity and costs per unit indicated, as non-recurring charges (NRC) and monthly recurring charges (MRC), as applicable. Charges not included in quote shall not be added to subsequent invoices, and U.S. Government shall not be obligated to pay charges that are not specified in quote and authorized in resultant Order or Circuit Demand. A Contractor’s/TP’s quote may be determined unacceptable if the quote takes exception to any of the terms of the Inquiry, if the quote fails to meet any requirements, or if the quote presents any ambiguity or uncertainty regarding the Contractor’s/TP’s intention to meet requirements.
All charges quoted shall be understood to be firm fixed prices for the life of the contract. Firm fixed price quotes must account for all applicable charges (e.g., charges from Subcontractors or other Contractors/TPs, taxes, surcharges, universal service fund, fees, etc.), and these charges may not be billed separately. Quote should state up front whether the quote contains tariff charges. Charges required by tariffs must be identified in the quote, with the effective date, National Exchange Carrier
Association (NECA) ; and include the applicable tariff reference by name, section, paragraph, revision number, and effective date of each page. Additionally, any future tariff changes will be electronically submitted, with the tariff transmittal and accompanying pages, to disa.scott.ditco.mbx.tariffs@mail.mil, subject line: tariff transmittal.
All quotes shall be provided in English.
ACCEPTABLE CONTRACTOR/TELECOMMUNICATIONS PROVIDER (TP) RESPONSE: “UNDERSTAND, WILL
COMPLY” and provide the required information.
STANDARD PROVISION - 08 - ALLA PROCEDURE - JUL 2009
One or more end points of this circuit terminate in NATO countries that have National Long Lines Agencies (NALLAs) and
NALLA accredited Telecommunication Providers (TPs). As a member and signatory in North Atlantic Treaty Organization
(NATO), the U.S. Department of Defense acquires its military telecommunication services in accordance with NATO requirements specified in Alliance Long Lines Activity (ALLA) handbook. Therefore, only TPs accredited by NALLAs of respective NATO countries will be eligible to receive any Order or Circuit Demand resulting from this Inquiry, for NATO country portions of this circuit. Additionally, only NALLA accredited TPs can be used as subcontractor TP in NATO countries. In NATO countries having no NALLA and/or no NALLA accredited TP, quotes from TPs possessing authorization to provide communication services from appropriate national authority will be considered. Quotes shall identify portions of service that will be provided using TP’s own facilities as well as those that will be provided by subcontractor TPs, and shall identify all subcontractor TPs. Additionally, quotes shall provide evidence TP and all subcontractor TPs possess required
NALLA accreditations or national authority authorizations for countries where this circuit terminates. Evidence of such
NALLA accreditation and national authority authorizations for TP and all subcontractor TPs is a definitive responsibility criterion.
ACCEPTABLE TELECOMMUNICATIONS PROVIDER (TP) RESPONSE: “UNDERSTAND,” and identify all portions of service provided by TP and all portions of the service provided by subcontractor TPs, plus provide evidence that TP and all subcontractor TPs possess required NALLA accreditations and national authority authorizations.
STANDARD PROVISION - 11 - ONE-STOP-SHOPPING/END-TO-END SERVICE VS HALF
CIRCUITS ALLA PROCEDURE - JUL 2009
U.S. Government’s preference is to obtain this service on a “One-Stop-Shopping” (OSS) or end-to-end service basis. Under an
OSS or end-to-end arrangement, Telecommunications Provider (TP) receiving this contract shall have total responsibility for end-to-end technical sufficiency and invoicing (i.e., end-to-end provisioning, restoral/maintenance, and invoicing) for entire service. For circuits having one or more end points in a NATO country that has a NALLA and one or more NALLA accredited
TPs, OSS/end-to-end quotes will only be considered when submitted by such NALLA accredited TPs. Government may consider half circuit quotes when it is unsuccessful in obtaining an OSS/end-to-end quote, when OSS/end-to-end quote charges cannot be determined to be fair and reasonable, or when determined to be in best interest of U.S. Government. Therefore, all
TPs are advised to submit a half circuit quote in addition to any OSS/end-to-end quote they are authorized to provide. All half-circuit quotes must identify TPs that they have coordinated with to provide complete service, along with agreed upon circuit midpoint.
ACCEPTABLE TELECOMMUNICATIONS PROVIDER (TP) RESPONSE: “UNDERSTAND,” and identify the coordinating TP and the circuit midpoint for half circuit quotes.
STANDARD PROVISION - 17 - SUBMISSION OF QUOTES - AUG 2015
Due date for quotes in response to this Inquiry is found in Paragraph V. DITCO’s required method of receiving quotes is via
Integrated Defense Enterprise Acquisition System (IDEAS), unless Inquiry specifically authorizes the use of other electronic media. However, Contractors/TPs not authorized to obtain a PKI certificate may submit their quotes to DITCO Scott via e-mail to the attention of the DITCO Scott Contract Specialist, to DITCO Pacific via e-mail to the attention of the DITCO Pacific
Contract Specialist, to DITCO Europe/Stuttgart via email at disa.stuttgart.ditco.mbx.pl511@mail.mil, or to DITCO
Europe/Bahrain at disa.stuttgart.ditco.mbx.pl52@mail.mil.
ACCEPTABLE CONTRACTOR/TELECOMMUNICATIONS PROVIDER (TP) RESPONSE: “UNDERSTAND,” and provide Quote by due date and time.
STANDARD PROVISION - 21 - QUOTES RECEIVED AFTER DUE DATE AND
WITHDRAWALS OF QUOTES - AUG 2015
It is the responsibility of each Contractor/Telecommunication Provider (TP) to provide its quote (or any modification or revision) to the DITCO Contracting Office that issued Inquiry by quote due date. Accordingly, U.S. Government is not obligated to consider any quote or revised quote received after quote due date.
Contractor/TP may withdraw its quote at any time prior to U.S. Government issuing an Order or Circuit Demand. Upon receipt of a written quote withdrawal notification from a Contractor/TP, quote will be withdrawn and eliminated from further consideration by U.S. Government.
STANDARD PROVISION - 23 - EVALUATION OF QUOTES-TECHNICAL/SERVICE
DATE/PRICE - AUG 2015
Quotes received in response to this Inquiry will be evaluated for technical acceptability, ability to meet required service date, and total price. Government contractor support may be utilized to analyze technical and price aspects of quotes submitted. The
Government intends to issue an Order to the Contractor/Telecommunication Provider (TP) whose quote is determined to be the lowest priced, technically acceptable quote that meets the government’s service date. In the event that none of the quotes meets required service date, U.S. Government may consider quotes that agree to provide service on a date later than required service date. For evaluation purposes, total price will be determined by adding charges contained in quote (NRC, MRC, and any expedite charges) for the total estimated contract period (i.e., estimated service life or term, as appropriate). U.S. Government intends to evaluate quotes and issue an Order or Circuit Demand without negotiations. Therefore, initial quote submitted should contain Contractor’s/ TP’s best technical solution, service date, and price. However, U.S. Government reserves the right to conduct negotiations, if determined necessary by Contracting Officer.
STANDARD PROVISION - 25 - EVALUATION OF QUOTES-FOREIGN CURRENCY - MAR
Quotes containing charges in foreign currency will be converted to U.S. currency for price evaluation purposes. Foreign currency conversion rates will be obtained from OANDA web site (www.oanda.com). Conversion rate in effect on final quote due date will be used for evaluation of all quotes containing foreign currency.
STANDARD PROVISION - 27 - APPROVALS AND PERMITS - AUG 2013
Contractor/Telecommunications Provider (TP) receiving this contract shall be responsible for having or obtaining all approvals and permits necessary to provide this service. Inability of Contractor/TP to obtain any such approval or permit shall not be a valid basis for not meeting service date or providing service. Failure of a Contractor/TP to obtain any approval or permit necessary to provide this service may result in termination of this contract by U.S. Government for default at no cost to U.S.
Government and/or receipt of a negative past performance rating.
ACCEPTABLE CONTRACTOR/TELECOMMUNICATIONS PROVIDER (TP) RESPONSE: “UNDERSTAND/WILL
COMPLY.
STANDARD PROVISION - 30 - CONTRACT PERIOD - AUG 2015
**This contract for this telecommunications service shall have an estimated contract period of _60_ months. However, this estimated contract period is not guaranteed. The minimum service period shall be one month. Accordingly, after meeting minimum service period, U.S. Government may discontinue service, at no additional cost to U.S. Government. U.S.
Government will provide Contractor/Telecommunications Provider (TP) 30 days notice prior to discontinuing service.
Quotes that do not accept the minimum one month service period may be excluded from the competition and found unacceptable. In the event U.S. Government is unable to obtain quotes that meet this minimum service period, U.S.
Government may consider quotes with a minimum service period greater than one month.
**Note: The estimated service life of 60 months shall begin on the date of award; It shall not begin when the circuit is installed.
COMPLY.”
STANDARD PROVISION - 33 - COMPLETION NOTICE - DITCO EUROPE - AUG 2015
Contractor/Telecommunications Provider (TP) shall provide a completion notice to DITCO within 72 hours of delivering service to U.S. Government acceptance activity. The customer then has an additional 72 hours to notify DITCO if they disagree that the service is complete. A completion notice must include following information: (1) DITCO CSA number, (2)
DITCO TSR number, (3) type of action, (4) contracted service date, (5) date service was delivered to and accepted by U.S.
Government acceptance activity; (6) commercial circuit identifier or phone number; (7) Contractor's/TP's trouble reporting number; (8) Contractor bill cycle end date; (9) a listing of any equipment installed on government premises by location and any deviations from service ordered; (10) name, phone number, and e-mail address U.S. Government representative (non-DITCO) that accepted service; and (11) Contractor/TP POC name, phone number, and e-mail address. Unless deviations are identified, completion notice will serve as Contractor/TP's confirmation that service was provided in accordance with contract. A follow-up completion notice will be required when deviations are cleared. Failure of Contractor/TP to provide completion notice may result in delay in invoice payment. DITCO Europe/Stuttgart’s preferred method of receiving a completion notice is via
Integrated Defense Enterprise Acquisition System (IDEAS). However, Contractors/TPs not authorized to obtain a PKI certificate may submit their completion notice to DITCO Europe/Stuttgart via email at disa.stuttgart.ditco.mbx.pl511@mail.mil, or to DITCO Europe/Bahrain at disa.stuttgart.ditco.mbx.pl52@mail.mil.
ACCEPTABLE CONTRACTOR/TELECOMMUNICATION PROVIDER (TP) RESPONSE: "UNDERSTAND/WILL
COMPLY."
STANDARD PROVISION - 37 - JEOPARDY NOTICE - AUG 2015
Contractor/Telecommunications Provider (TP) shall immediately provide a Jeopardy Notice via Integrated Defense Enterprise
Acquisition System (IDEAS) prior to the contracted service date as soon as Contractor/TP becomes aware contract service date may not be or cannot be met. A Jeopardy Notice must include following information: (1) DITCO CSA number; (2) TSR number; (3) contracted service date; (4) explanation of why contracted service date may not be or cannot be met; (5) revised service date requested; and (6) name, phone number, and email address of Contractor/TP representative that can be contacted for any questions concerning the Jeopardy Notice. DITCO’s preferred method of receiving a jeopardy notice is via Integrated
Defense Enterprise Acquisition System (IDEAS). However, Contractors/TPs not authorized to obtain a PKI certificate may submit their jeopardy notice via e-mail to the attention of the DITCO-Scott Contracting Specialist, the DITCO-Pacific Contract
Specialist, disa.stuttgart.ditco.mbx.pl511@mail.mil or disa.stuttgart.ditco.mbx.pl52@mail.mil as applicable. DISA’s acknowledgement of the Contractor/TP’s representation of delayed performance is not an explicit or implicit acceptance of the performance delay nor is it a waiver of any rights or remedies allowed under the contract, the FAR, or applicable case law.
Moreover, it is not an acknowledgment that DISA is responsible for any part of the Contractor/TP’s delayed performance.
ACCEPTABLE CONTRACTOR/TELECOMMUNICATION PROVIDER (TP) RESPONSE: “UNDERSTAND/WILL
STANDARD PROVISION - 38 - STATUS REPORT - AUG 2013
Due to the criticality of this telecommunications service, Contractor/Telecommunications Provider (TP) shall provide an updated status report to DITCO contracting officer weekly. Status report shall include (1) DITCO CSA number, (2) TSR number, (3) contracted service date, (4) explanation of current status of telecommunications service installation and how current status provides assurance that contracted service date will be met, and (5) name, phone number, and e-mail address of
Contractor/TP representative to contact for any questions concerning the status report.
STANDARD PROVISION - 39 - CIRCUIT DOCUMENTATION - AUG 2015
Contractor/Telecommunications Provider (TP) shall provide complete circuit routing maps for the end-to-end circuit documenting physical routing and location of supporting equipment and facilities. Contractor/TP maps/diagrams provided for quotes must reflect the most accurate information and route details available at the time the quote is submitted. Information provided in the maps will be used to determine if the Contractor/TP’s quote meets the technical requirements identified in the
Inquiry. Lack of required information or detail may result in the vendor solution to be determined technically unacceptable.
Contractor/TP will provide updated maps/diagrams to DITCO no later than 30 days after the vendor sends the Notice of
Completion (NOC), if there have been any authorizes changes made to the original fiber path/routes or any technical details
(including round-trip latency) provided in the original quote. If no changes have been made, vendor will include a statement on their NOC that the original diagrams/maps provided reflect the as-built route/path/configuration.
Such documentation shall be provided to the DITCO contracting office and contact at each service point post award and prior to acceptance by the U.S. Government acceptance activity.
Specific documentation requirements:
A. Customer premise equipment (CPE) and interface at each termination location.
B. Route maps showing the physical diversity requirements are being met.
C. Major equipment and facilities locations (i.e., multiplexers, switches, central offices, etc.) location and precise fiber distance between the commercial demark and the nearest Servicing Wire Center (SWC) or Central Office (CO) must be included for each end of the leased portion of the circuit.
D. Location and address of all gateway Central Offices (hand-off between carriers).
E. Cable head, cable landing stations, and cable stations, if applicable.
F. Location of manholes and handholes in relationship to physical landmarks such as buildings, streets, bridges, etc. (where diversity requirements necessitate that level of detail).
G. Locations of slack coils to facilitate response to maintenance requirements.
H. Earth stations and satellite, if applicable.
This documentation must be provided in electronic format. Acceptable formats are Microsoft Office (PowerPoint, Word, and
Excel), Visio, AutoCAD and Adobe PDF.
COMPLY.” And provide the required information and maps/drawings.
STANDARD PROVISION - 41 - SCHEDULED OUTAGES - AUG 2013
To ensure this service is available to support U.S. Government requirements, Contractor/Telecommunications Provider (TP) shall utilize alternate or spare facilities whenever possible to eliminate or minimize service interruptions. However, when a scheduled service interruption cannot be avoided, Contractor/TP shall obtain the approval of appropriate approval authority before initiating any scheduled outage. To obtain such approval, a written “circuit release request” must be submitted to appropriate approval authority at least 21 calendar days prior to requested circuit release date.
When an interruption of service is required to correct hazardous or degraded conditions, a 48-hour prior notification is required, if practicable. Contractor/TP shall notify the U.S. Government service acceptance activity as soon as it is known that a service interruption will occur. The request from Contractor/TP must include the same information as identified below, and additionally, identify the hazardous or degraded conditions that exist which preclude providing the U.S. Government with 21-day advance notice.
In emergency situations, when loss of life or property might occur through lack of immediate action, Contractor/TP must make every reasonable attempt to notify the U.S. Government service acceptance activity identified on the CSA immediately, and coordinate arrangements for the service interruption to the maximum extent possible. Within 5 business days of the interruption, Contractor/TP must submit the same information as identified below, and additionally, identify the emergency conditions that existed which precluded providing the U.S. Government with 21-day advance notice.
“Circuit Release Request” must include following information: (1) Contractor/TP requesting circuit release, and name and phone number of Contractor/TP representative responsible for managing circuit release; (2) DITCO CSA number of circuit for which release is being requested; (3) date and inclusive times of scheduled circuit release, along with an alternate circuit release date and time; (4) purpose of scheduled circuit release; (5) statement indicating all equipment, parts, and/or supplies required to complete action are on-hand, or their expected delivery date; (6) statement indicating that all avenues of bypass capability (e.g., alternate facilities, spare facilities, etc.) Have been considered; and (7) estimated maximum recovery time to restore circuit.
The authority for approving circuit releases for this service is U.S. Government CCO/CMO. Failure of Contractor/TP to obtain an approved circuit release prior to initiating a scheduled outage may result in U.S. Government termination of this contract for default at no cost to U.S. Government and/or receipt of a negative past performance rating.
STANDARD PROVISION - 42 - CONSIDERATION - AUG 2015
Upon Contractor/telecommunications Provider (TP) caused failure to provide telecommunications service by the specified date in the contract, failure to make progress as to endanger performance by that date, or failure to comply with any contract terms or conditions; U.S. Government may cancel or terminate this contract pursuant to contract clause DFARS 252.239-7007 at no cost to the Government. However, U.S. Government may elect to waive its right to cancel or terminate and request
Contractor/TP to provide consideration to U.S. Government in lieu thereof. Consideration will be negotiated on a case-by-case basis. If Contractor/TP fails to meet the service date or comply with any contract terms or conditions and U.S. Government elects to request consideration, Contractor/TP hereby agrees to negotiate in good faith and provide such consideration. Quotes, which fail to accept this standard provision, may be excluded from consideration for award.
STANDARD PROVISION - 44 - SYSTEM FOR AWARD MANAGEMENT REGISTRATION -
AUG 2013
(a) Definitions. As used in this clause-
"Central Contractor Registration (CCR) database" means the retired primary Government repository for Contractor information required for the conduct of business with the Government.
"Commercial and Government Entity (CAGE) code" means-
(1) A code assigned by the Defense Logistics Agency (DLA) Logistics Information Service to identify a commercial or
Government entity; or
(2) A code assigned by a member of the North Atlantic Treaty Organization that DLA records and maintains in the CAGE master file. This type of code is known as an "NCAGE code."
"Data Universal Numbering System (DUNS) number" means the 9-digit number assigned by Dun and Bradstreet, Inc. (D&B) to identify unique business entities.
"Data Universal Numbering System+4 (DUNS+4) number" means the DUNS number means the number assigned by D&B plus a 4-character suffix that may be assigned by a business concern. (D&B has no affiliation with this 4-character suffix.) This
4-character suffix may be assigned at the discretion of the business concern to establish additional SAM records for identifying alternative Electronic Funds Transfer (EFT) accounts (see the FAR at Subpart 32.11) for the same concern.
"Registered in the SAM database" means that-
(1) The Contractor has entered all mandatory information, including the DUNS number or the DUNS+4 number, into the
SAM database;
(2) The Contractor's CAGE code is in the SAM database; and
(3) The Government has validated all mandatory data fields, to include validation of the Taxpayer Identification Number
(TIN) with the Internal Revenue Service (IRS), and has marked the record "Active". The Contractor will be required to provide consent for TIN Attachment, Page 1 of 4 validation to the Government as a part of the SAM registration process.
"System for Award Management (SAM)" means the primary Government repository for prospective federal awardee information and the centralized Government system for certain contracting, grants, and other assistance related processes. It includes-
(1) Data collected from prospective federal awardees required for the conduct of business with the Government;
(2) Prospective Contractor submitted annual representations and certifications in accordance with FAR Subpart 4.12; and
(3) The list of all parties suspended, proposed for debarment, debarred, declared ineligible, or excluded or disqualified under the nonprocurement common rule by agencies, Government corporations , or by the Government Accountability Office.
(b)
(1) The Contractor shall be registered in the SAM database prior to submitting an invoice and through final payment of any contract, basic agreement, basic ordering agreement, or blanket purchasing agreement resulting from this solicitation.
(2) The SAM registration shall be for the same name and address identified on the contract, with its associated CAGE code and DUNS or DUNS+4.
(3) If indicated by the Government during performance, registration in an alternate system may be required in lieu of SAM.
(c) If the Contractor does not have a DUNS number, it should contact Dun and Bradstreet directly to obtain one.
(1) A Contractor may obtain a DUNS number-
(i) Via the internet at http://fedgov.dnb.com/webform or if the Contractor does not have internet access, it may call Dun and Bradstreet at 1-866-705-5711 if located within the United States; or
(ii) If located outside the United States, by contacting the local Dun and Bradstreet office. The Contractor should indicate that it is a Contractor for a U.S. Government contract when contacting the local Dun and Bradstreet office.
(2) The Contractor should be prepared to provide the following information:
(i) Company legal business name.
(ii) Tradestyle, doing business, or other name by which your entity is commonly recognized.
(iii) Company physical street address, city, state and Zip Code.
(iv) Company mailing address, city, state and Zip Code (if separate from physical).
(v) Company telephone number.
(vi) Date the company was started.
(vii) Number of employees at your location.
(viii) Chief executive officer/key manager.
(ix) Line of business (industry).
(x) Company Headquarters name and address (reporting relationship within your entity).
(d) Reserved.
(e) Processing time for registration in SAM, which normally takes five business days, should be taken into consideration when registering. Contractors who are not already registered should consider applying for registration at least two weeks prior to invoicing.
(f) The Contractor is responsible for the accuracy and completeness of the data within the SAM database, and for any liability resulting from the Government's reliance on inaccurate or incomplete data. To remain registered in the SAM database after the initial registration, the Contractor is required to review and update on an annual basis from the date of initial registration or subsequent updates its information in the SAM database to ensure it is current, accurate and complete. Updating information in the SAM does not alter the terms and conditions of this contract and is not a substitute for a properly executed contractual document.
(g)
(1)
(i) If a Contractor has legally changed its business name, "doing business as" name, or division name (whichever is shown on the contract), or has transferred the assets used in performing the contract, but has not completed the necessary requirements regarding novation and change-of-name agreements in Subpart 42.12, the Contractor shall provide the responsible Contracting
Officer sufficient documentation to support the legally changed name with a minimum of one business day's written notification of its intention to-
(A) Change the name in the SAM database;
(B) Comply with the requirements of subpart 42.12 of the FAR; and
(C) Agree in writing to the timeline and procedures specified by the responsible Contracting Officer.
(ii) If the Contractor fails to comply with the requirements of paragraph (g) (1) (i) of this clause, or fails to perform the agreement at paragraph (g) (1) (i) (C) of this clause, and, in the absence of a properly executed novation or change-of-name agreement, the SAM information that shows the Contractor to be other than the Contractor indicated in the contract will be considered to be incorrect information within the meaning of the "Suspension of Payment" paragraph of the electronic funds transfer (EFT) clause of this contract.
(2) The Contractor shall not change the name or address for EFT payments or manual payments, as appropriate, in the SAM record to reflect an assignee for the purpose of assignment of claims (see FAR Subpart 32.8, Assignment of Claims). Assignees shall be separately registered in the SAM database. Information provided to the Contractor's SAM record that indicates payments, including those made by EFT, to an ultimate recipient other than that Contractor will be considered to be incorrect information within the meaning of the "Suspension of payment" paragraph of the EFT clause of this contract.
(h) Contractors may obtain information on registration and annual confirmation requirements via the SAM accessed through https://www.acquisition.gov or by calling 866-606-8220, or 334-206-7828 for international calls.
ACCEPTABLE VENDOR/TELECOMMUNICATIONS PROVIDER (TP) RESPONSE: “UNDERSTAND/WILL
STANDARD PROVISION - 50 - INVOICING - IDEAS - MAR 2014
Contractor/Telecommunications Provider (TP) must submit invoices with the CSA number in the proper invoicing format.
IDEAS CSAs are 11 to 13 characters long. In order to invoice correctly the proper spacing is required. After the telco (2-4 alpha numeric characters) there needs to be 7 spaces before the circuit number (6 digits).
Examples:
IDEAS CSA INVOICE CSA
MELA123456EBM MELA 123456EBM (7 SPACES)
MEL123456EBM MEL 123456EBM (8 SPACES)
ME123456EBM ME 123456EBM (9 SPACES)
ACCEPTABLE CONTRACTOR/TELECOMMUNICATIONS PROVIDER (TP) RESPONSE:
"UNDERSTAND/WILL COMPLY."
Attachment A - Additional Documents
Attachments for this section start after this page.
252.204-7008 Compliance with Safeguarding Covered Defense Information Controls.
As prescribed in 204.7304(a), use the following provision:
COMPLIANCE WITH SAFEGUARDING COVERED DEFENSE INFORMATION
CONTROLS (DEC 2015)
(a) Definitions. As used in this provision—
“Controlled technical information,” “covered contractor information system,” and “covered defense information” are defined in clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting.
(b) The security requirements required by contract clause 252.204-7012, Covered Defense Information and Cyber Incident Reporting, shall be implemented for all covered defense information on all covered contractor information systems that support the performance of this contract.
(c) For covered contractor information systems that are not part of an information technology (IT) service or system operated on behalf of the Government (see 252.204-7012(b)(1)(ii))—
(1) By submission of this offer, the Offeror represents that it will implement the security requirements specified by National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations” (see http://dx.doi.org/10.6028/NIST.SP.800-171), not later than December 31, 2017.
(2)(i) If the Offeror proposes to vary from any of the security requirements specified by NIST SP 800-171 that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer, the Offeror shall submit to the Contracting Officer, for consideration by the DoD Chief Information Officer (CIO), a written explanation of—
(A) Why a particular security requirement is not applicable; or
(B) How an alternative but equally effective, security measure is used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection.
BF26FEB166040
http://www.acq.osd.mil/dpap/dars/dfars/html/current/204_73.htm http://www.acq.osd.mil/dpap/dars/dfars/html/current/252204.htm http://www.acq.osd.mil/dpap/dars/dfars/html/current/252204.htm http://www.acq.osd.mil/dpap/dars/dfars/html/current/252204.htm http://dx.doi.org/10.6028/NIST.SP.800-171
(ii) An authorized representative of the DoD CIO will adjudicate offeror requests to vary from NIST SP 800-171 requirements in writing prior to contract award. Any accepted variance from NIST SP 800-171 shall be incorporated into the resulting contract.
(End of provision)
252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting.
As prescribed in 204.7304(c), use the following clause:
SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT
REPORTING (DEC 2015)
(a) Definitions. As used in this clause—
“Adequate security” means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.
“Compromise” means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.
“Contractor attributional/proprietary information” means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.
“Contractor information system” means an information system belonging to, or operated by or for, the Contractor.
“Controlled technical information” means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements http://www.acq.osd.mil/dpap/dars/dfars/html/current/204_73.htm on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.
“Covered contractor information system” means an information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.
“Covered defense information” means unclassified information that—
(i) Is—
(A) Provided to the contractor by or on behalf of DoD in connection with the performance of the contract; or
(B) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract; and
(ii) Falls in any of the following categories:
(A) Controlled technical information.
(B) Critical information (operations security). Specific facts identified through the Operations Security process about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively so as to guarantee failure or unacceptable consequences for friendly mission accomplishment (part of Operations Security process).
(C) Export control. Unclassified information concerning certain items, commodities, technology, software, or other information whose export could reasonably be expected to adversely affect the United States national security and nonproliferation objectives. To include dual use items; items identified in export administration regulations, international traffic in arms regulations and munitions list; license applications; and sensitive nuclear technology information.
(D) Any other information, marked or otherwise identified in the contract, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies (e.g., privacy, proprietary business information).
“Cyber incident” means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.
“Forensic analysis” means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.
“Malicious software” means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.
“Media” means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which information is recorded, stored, or printed within an information system.
‘‘Operationally critical support’’ means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.
“Rapid(ly) report(ing)” means within 72 hours of discovery of any cyber incident.
“Technical information” means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data-Non Commercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.
(b) Adequate security. The Contractor shall provide adequate security for all covered defense information on all covered contractor information systems that support the performance of work under this contract. To provide adequate security, the Contractor shall—
(1) Implement information systems security protections on all covered contractor information systems including, at a minimum—
(i) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government—
(A) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract; and
BF26FEB166040
http://www.acq.osd.mil/dpap/dars/dfars/html/current/252227.htm#252.227-7013 http://www.acq.osd.mil/dpap/dars/dfars/html/current/252239.htm
(B) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract; or
(ii) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1)(i) of this clause—
(A) The security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations,” http://dx.doi.org/10.6028/NIST.SP.800-171 that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer, as soon as practical, but not later than December 31, 2017. The Contractor shall notify the DoD CIO, via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award; or
(B) Alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection accepted in writing by an authorized representative of the DoD CIO; and
(2) Apply other information systems security measures when the Contractor easonably determines that information systems security measures, in addition to those identified in paragraph (b)(1) of this clause, may be required to provide adequate security in a dynamic environment based on an assessed risk or vulnerability.
(c) Cyber incident reporting requirement.
(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor’s ability to perform the requirements of the contract that are designated as operationally critical support, the Contractor shall—
BF26FEB166040
http://dx.doi.org/10.6028/NIST.SP.800-171 mailto:osd.dibcsia@mail.mil
(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor’s network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor’s ability to provide operationally critical support; and
(ii) Rapidly report cyber incidents to DoD at http://dibnet.dod.mil.
(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at http://dibnet.dod.mil.
(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx.
(d) Malicious software. The Contractor or subcontractors that discover and isolate malicious software in connection with a reported cyber incident shall submit the malicious software in accordance with instructions provided by the Contracting Officer.
(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.
(f) Access to additional information or equipment necessary for forensic analysis.
Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.
(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.
BF26FEB166040
http://dibnet.dod.mil/ http://dibnet.dod.mil/ http://iase.disa.mil/pki/eca/Pages/index.aspx
(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.
(i) Use and release of contractor attributional/proprietary information not created by or for DoD.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .