MPACS_Amendment 05.doc
DOC document 695 KB Posted
- Solicitation number
- FA4600-11-R-0006_VAQRSS
About this file
MPACS Amendment 05 with responses to questions from industry.
View the file
Other files
Show 40 more
Latest 50 of 79 listed here. See the rest on GovTribe.
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
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
The following items are applicable to this modification:
PURPOSE OF AMENDMENT
1. The purpose of the amendment is to respond to industry questions. Changes to documents Sec J, Atch 1, PWS and Sec J, Atch 17, Representative SCRs in the Summary of Changes are marked with a bar on the right side of the page. Sec J, Atch 18, WBS, is change in its entirety and Sec J, Atch 3, DD254, block 11a is changed to “No.”
| Question |
| Section |
| Comment/Question |
| Govermment Response |
| Q4.1 |
| Sec I |
| Section I contains DFAR 252.209-7008 (DEC 2010) Notice of Prohibition relating to Organizational Conflict of Interest – Major Defense Acquisition Program. |
RFP Section J, Attachment 1 Performance Work Statement does not contain any description of system engineering and technical assistance (SETA) efforts per 209.571-1.
Recommend that clause 252.209-7008 be removed as it does not apply to the work described in the PWS. If not, please provide clarification on where SETA efforts are described in the PWS.
Clause DFARs 252.209-7008 will remain in the solicitation.
| Q5.1 |
| Sec J, Pricing Model |
| There are no equations in Rows 150-152 on the Grand Total Tab. Could the Government provide an updated cost model? |
| While we do require the total cost data and a formula should be inserted, when we built the formula it pulled the total budget data which some offerors interpreted as a fixed number not required to be estimated. As a result, we removed the formula to allow the offeror to show what items are included in the offeror’s estimate. |
| Q5.2 |
| Sec J, Pricing Model |
| The Cells in B60 and C60 on the Price Model are pointing to the wrong cells on tab CLIN 0010. Could the Government provide an updated cost model? |
| Corrected in latest version of Price Model. |
| Q5.3 |
| Sec L1.3.1 |
| Can we assume that CLIN 0006, Pre-Priced Option Task Order – Data Mover Virtual Implementation, would come out of the *Potential 3400/3600 Efforts* line item in the Government Budget specified in Section L1.3.1? Please clarify. |
| The budget is for information purposes only. The proposal and Pre-Priced Option Task Orders are not to be related to the budget and Government Populated CLINs within the RFP. Future task orders will be awarded from the CLINS X003 and X004. |
| Q5.4 |
| Sec L1.3.1 |
| Can we assume that CLIN 0010, Pre-Priced Option Task Order – Development Approach, would come out of the *Potential 3400/3600 Efforts* line item in the Government Budget specified in Section L1.3.1? Please clarify. |
| The budget is for information purposes only. The proposal and Pre-Priced Option Task Orders are not to be related to the budget and Government Populated CLINs within the RFP. Future task orders will be awarded from the CLINS X003 and X004. |
| Q5.5 |
| Sec L6.1 |
| In Section L6.1, CLIN 0010 is not included in that paragraph. We assume it should be. Please confirm. |
| CLIN 0010 is added to Sec L6.1. |
| Q5.6 |
| Sec L6.7 |
| In Section L6.7, CLIN 0010 is stated as a Target Fee of 6.5%. Section B states 10%. Please confirm that the Target Fee on CLIN 0010 should be 10%. |
| Sec L6.7: 6.5% is changed to 10%. |
| Q5.7 |
| Sec L1.3.1 |
| In L1.3.1, please confirm whether or not pre-priced task orders offered on CLINs 0006 and 0010 are the first X003 Development and X004 Enhancement task orders described in the note: *Potential 3400/3600 Efforts will be negotiated for Future Development Task Orders (CLIN X003), Future Enhancement Task Orders (CLIN X004), and Future FFP Taskings (CLIN X008) |
If yes, should the proposed price for CLIN 0003 and CLIN 0004 be decremented by the prices for CLINs 0010 and 0006, respectively, so that when added together per L6.13 and L6.14:
0003 + 0010 = $2.4M
0004 + 0006 = $2.4M
If no, where should we account for the prices of CLINs 0006 and 0010 so that the total priced value of the proposal does not exceed $62.34M per L1.3.1.
No, the offeror should propose the split of the funds provided in the Potential 3400/3600 budget shown in Para L1.3.1. and represented in CLIN 3/Para L.6.13, CLIN 4/L.6.14, and CLIN 8/Para
L6.15. The Offeror prices for the pre-priced task orders should not be included in the $62.3M shown in Para L1.3.1.
| Q5.8 |
| Sec J, Atch 14, Price Model |
| Attachment 14 Price Model structure does not allow for Labor Cost escalation during Option 5, which appears to be a pre-priced 6 month extension re: FAR 52.217-8. For cost-type CLINs proposed using forward pricing rates approved by DCMA, this may be inconsistent with an offeror’s DCMA approved cost accounting disclosure statements and pricing practices. Are offerers allowed to modify Attachment 14 to comply with DCMA approved cost accounting disclosure statements and pricing practices? |
| Yes, the offerors are allowed to modify Attachment 14. However, please provide the rationale for the modification and description of the changes. |
| Q5.9 |
| Sec J, Atch 18 WBS and Atch 14 Price Model |
| 1) Please clarify the requested WBS mapping (using Attachment 18) for the following columns in Attachment 14 Price Model – “CLIN 0001 Base Year Breakdown” Columns. They do not currently appear in Attachment 18 WBS: |
a. DATA/CDRLS
b. Processing Engineering
c. Contractor Dev Test & Eval
d. Gov Dev Test & Eval
2) When reading Attachment 18 WBS, the changes in indentation formatting and numbering within the WBS descriptions has led to differences in interpretation of the requested levels and roll-up summaries of cost. Please provide a clarified WBS explanation if the following statements are not accurate (using CLIN 0001 as an example):
a. WBS Descriptions using “Year N-1” reference WBS that must be tracked by release within “Year N”, examples:
i. “Year N-1” = Release 1 in year N
ii. In a future WBS, “Year N-2” = Release 2 in year N
b. WBS 1.0 Description should be changed to “Year N” and this WBS level represents the top-level roll-up level for all of CLIN 0001
c. 1.1 is for the first release under CLIN 0001.
d. In a future WBS “1.2” would be used for the second release under CLIN 0001
e. What is shown as WBS “1.2” should be viewed as “1.20”
f. What is shown as WBS “1.3” should be viewed as “1.30”
g. 1.111 rolls up to 1.11 which rolls up to 1.1
h. The Government only requests costs for 1.111 Code SCRs to be tracked by software release. All other WBS (1.12 – 1.30) are tracked by year and not subtotaled by release within a year.
Specifically, there is no request to track WBS 1.121, 1.122, 1.123, 1.191, or 1.201 by releases within a year.
1) All categories included in the Price Model should be included in the Attachment 18 WBS. We will modify to include the data.
2) The WBS descriptions were not meant to follow any historical release patterns but to follow the following descriptions:
a. “Year N-1” was meant to describe the first Government Fiscal Year Cost and N-2 etc all subsequent years of the contract. The 1.1 section should link the delivery or release cost with the Fiscal Year. It is understood that in some cases a delivery or release may run into the next fiscal year. During execution the program office and offeror will discuss how best to handle this situation.
b. No, this does not represent the CLIN structure. It only represents the first full year of Government costs broken out by the different functional area.
c. (See response b.)
d. (See response b.)
e. Yes.
f. Yes.
g. Yes.
| Q5.10 |
| Sec J, Atch 17, SCRs |
| Amendment 0004, Section J, Attachment 17 provides an updated list of SCRs associated with AWPS. Review of this list indicates what appears to be duplicate entries as follows. Can the government confirm whether the SCRs identified are duplicates or intended to be separate SCRs? |
The numbers shown in the left-hand column were generated by simply numbering the Amendment 4 SCR list starting at 1.
SCRs 24 & 46 are duplicates and will be corrected in a new release of the SCRs List.
Q5.10 continued:
From the last row on page 22 and the second row of page 26 these two entries are identical
| 24 |
| Enhancement |
| Reports |
| Compare values in Damage Calculation |
| On the Damage Calculation window, allow selection of 1 DGZ with 2 weapon system inputs. Show the output to allow side-by-side comparison. |
| 46 |
| Enhancement |
| Reports |
| Compare values in Damage Calculation |
| On the Damage Calculation window, allow selection of 1 DGZ with 2 weapon system inputs. Show the output to allow side-by-side comparison. |
| Q5.11 |
| Sec J, Atch 17, SCRs |
| The following SCR references SCR 2201 that is not part of the bidder’s library. Can the government provide the text and associated documentation relative to SCR 2201? |
| This reference should not be included in the SCR list. The reference will be removed. The offeror should only propose code hours for the effort. |
Q5.11 continued:
| 45 |
| Enhancement |
| Decision Handbook |
| Modify Decision Handbook for Overflight data |
| Web AWPS should report "Always", "Sometimes", and "Never" in the DH. |
Check to see if the grid should contain data for those values, too.
This change should be coordinated with 2201, which may affect the frequency of overflight.
| Q5.12 |
| PP Volume |
| Page 2, Item 1.a extends past Performance Volume for response to Small Business Relevancy Only to 7 July 2012 |
Page 4, Clarification C4.1 reflects Past Performance Volume is extended to 6 July 2012
Page 29, Table 2.0, Item III shows 7 July 2012.
Please confirm due date of 7 July 2012 (Saturday), per the RFP the Government will accept delivery until Monday 9 July 2012 by 4pm Central Time.
The response date for the Past Performance volume is 6 Jul 12.
| Q5.13 |
| Sec B |
| CPIF CLINS in Section B request the contractor to fill in the Share Ratio Above Target and Share Ratio Below Target. The Share Ratio in Attachment 5, Incentive Plan has multiple share ratio ranges for Underruns and Overruns of target cost. Please clarify what number or text entries the Government is looking for in Section B for Share Ratio Above and Share Ratio Below Target? (Recommend this just reference Attachment 5) |
| Reference Attachment 5 Incentive Fee Plan for MPACs Share Ratios and computation of Costs. |
Q5.14
Page 3, Q4.5 states in Government Response: “a sample of representative tasks with descriptions of the tasks available to be accomplished in one full option year (12 months).
Further in the response it states: “The total number of coding hours for the representative tasks is to be shown in the CLIN 0001 Base Year…”
Because CLIN 0001 Base Year is a nine (9) month effort per Section F and L1.3.1, please clarify how the 12 months of representative SCRs should be interpreted and used in the nine (9) month Base Year PoP.
The SCRs are a sample of the work for twelve months. The offeror will prorate the SCRs for nine months listed in the base year.
Q5.15
| Will the Government release an updated Price Model and Section B to reflect the changes described in Amendment 0002 Q A2.4? Changes to CLIN X010 Section B CLIN description, and change reference cell in the Price model Worksheet “Grand Total” cell B69, currently showing 6.5%, should show 10%. |
| Yes. |
| Q5.16 |
| Follow-up to Amendment 4 Q&A re: Place of Performance |
| 1) Please confirm that in the Government answer “development work” refers to the overall scope of CLINs X001, X003, X004, 0006, and 0010. |
2) The MPACS bidder’s library was distributed as a classified artifact, so the answer appears to conflict with the RFP DD254 Block 11a. “Contractor will…have access to classified information only at another contractor’s facility of a government activity” [emphasis on ‘only’]. If development work is expected to be performed at the contractor’s facility, and the code being used is classified, should DD254 block 11a be changed to “No”?
3) What are the events or criteria within CDT&E that are expected to be performed at USSTRATCOM?
1. Yes. The "development work" does refer to the overall scope.
2.Sec J, Atch 3, DD254: Block 11a is changed to “No” because all the development work is being done offsite in a classified environment.
3. Almost all of CDT&E is done here at STRATCOM because the software can tested in the STRATCOM environment. RFP, Sec J, Atch 1, PWS, para 3.4, stated the following, "Developmental T&E includes a Contractor Developmental Test and Evaluation (CDT&E) phase (part of which shall be accomplished in the government facility), Government Developmental Test and Evaluation (GDT&E) phase and
User Acceptance Test (UAT) phase."
2. All other terms and conditions remain the same.
SUMMARY OF CHANGES
SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS
The following have been modified:
ATCH 17, REPRE SCR WORKSHEET
Sec J, Attachment 17: Representative SCRs Worksheet
| Type |
| Component |
| Title |
| Description |
| Adaptive |
| Web AWPS |
| Configuration creation date |
| Customer would like to see the configuration creation date when selecting a new configuration in Web AWPS. |
| Adaptive |
| EADSIM |
| Missing Aimpoint when connecting |
| Some analysis users try to get an early start on processing, but some of the configurations have data problems. Modify PC AWPS to bypass the "missing aimpoint" error when connecting to allow the Analysis users to get to the Extended Air Defense Simulation (EADSIM) portion of AWPS. |
| Adaptive |
| C of E |
| Add new field to COE_OPT |
| Add new detect Y/N field to COE_OPT. |
| Corrective |
| Web AWPS |
| Resource Impact - Display axis labels as whole numbers. |
| Start Web AWPS, go to resource impact. View a chart with 3 resources. Chart axis will have labels with decimal values. Format the axis labels to be whole numbers. |
| Enhancement |
| Config Maint |
| Restrict functionality by user |
| Web AWPS should restrict certain capabilities from certain users. For example, it should not enable Configuration Maintenance for QR users who don't create configurations. |
One possible solution is to use WebLogic roles or groups and assign them as appropriate.
| Adaptive |
| Web AWPS |
| Web Map Search - Add target of type 'G' |
| Add a target type to the list of generic targets on the map search widget that has a type factor of 'G'. |
| Adaptive |
| Web AWPS |
| Web Map Search - Move generic targets from java to Enterprise Database (EDB) |
| The generic target list on the map search widget could be moved from the java code to the Enterprise Database (EDB). |
| Adaptive |
| Web AWPS |
| Web map draw or search across 180 degrees |
| ESRI problem impacting Web Map: |
Open the map in Web AWPS. Click Tools->Draw. Click on the draw circle icon. Draw a circle starting just east of -180 degrees and drag so that the circle crosses over the -180 degree line. This is the functionality required.
| Adaptive |
| Web AWPS |
| HPAC - Store Additional Fatality Data. |
| Store fatalities for all timing data to the COE_OPT table. Also use this data in the Decision Handbook. This data will be provided in multiple HPAC tab files. Currently, COE_OPT table (and HPAC files) only holds one value. |
| Adaptive |
| Web AWPS |
| Add weapon and booster from outside the circle search from the selected Option |
| Web AWPS Maps - In the Circle Search details page, add the weapons/booster (weapons outside the circle search) from the selected option. It should be displayed in a way to know if it's inside the circle or outside. |
| Adaptive |
| Web AWPS |
| Add more detail on the Output page of the Circle Search Function. |
| Web AWPS Maps - Part 1 of the report (damage expenctancy detail), add all the search criteria used to generate this data (location, search radius, r95, etc). Also state which option, DGZ, Facility and weapon were used for the comparison. |
| Enhancement |
| Web AWPS |
| Generation Times for Aircraft in Decision Handbook |
| Allow the user to enter a default Generation time for Aircraft Options in the Web Decision Handbook. |
| Enhancement |
| Web AWPS |
| Modify Decision Handbook for Overflight data |
| Web AWPS should look at the whole Launch Patrol Area (LPA) and the Nonoverflight areas to come up with: |
1. No Overflight = no overflight in nonoverflight and whole LPA 2. May Overfly Ctry = no overflight in nonoverflight and overflight in whole LPA Overflight of Ctry.
| Enhancement |
| Decision Handbook |
| Add overflight/impact frequency to DH |
| The Decision Handbook already reports which countries are overflown/impacted. The users would also like to know how often. Add the frequency (Always,Sometimes) to the document. Currently, "Never" countries are not reported, but can be added if desired. |
| Enhancement |
| C of E |
| Web COE - Allow Edit of NULL values |
| Currently Web AWPS modify doesn't allow editing of NULL values. |
The user would like to run COE before certain data is on the EDB. This will require NULL values to be modified.
| Corrective |
| AWPS |
| Mover: Multiple lock groups error |
| If a user is in multiple lock groups, the mover will ask which one he wants to use to create the destination configurations. After selecting one, an error message is displayed ("Either EOF or BOF is true. . ."). |
| Adaptive |
| AWPS |
| Change UOM for Mission fields |
| Change the display format for the following Mission Q&R fields to HH:MM:SS: |
MFLSW
MFLSWM
MPLW
MPLWM
| Enhancement |
| Web AWPS |
| Add chart for REL_OPT |
| Display a chart (bubble?) to display relationships within the REL_OPT table. |
Design considerations:
We could display it at the grid/tile/tree level and the option detail level (there is already a section for related options).
| Adaptive |
| Web AWPS |
| Web AWPS - Display Tercom data on map |
| Web AWPS Map - Display Tercom data on map. |
| Adaptive |
| Web AWPS |
| Web AWPS - Read Excel file with data and display on map. |
| Web AWPS Map - Read an Excel file with Lat/Lon data plus types and colors. Display this info on map. |
| Adaptive |
| Web AWPS |
| Move temporary files on app server |
| Mid-tier has requested that we do not store any files to $DOMAIN/tmp. If temporary files are required in Web AWPS, put them in the /tmp directory if they are truly temporary. If more permanent storage is required, there is also space in /mpasapps/Enterprise Database (EDB)##/. |
| Enhancement |
| Queries |
| Drag Keys From Excel to Build Query |
| Instead of typing the value in the Build Query window, the user would like to drop data from an Excel spreadsheet (multiple values). |
| Enhancement |
| Reports |
| Export Damage Calculation Window to Excel |
| Export the data from the Damage Calculation window to an Excel Spreadsheet. |
| Enhancement |
| Reports |
| Compare values in Damage Calculation |
| On the Damage Calculation window, allow selection of 1 DGZ with 2 weapon system inputs. Show the output to allow side-by-side comparison. |
| Enhancement |
| Web AWPS |
| Web Decision Handbook - SEAD/DEAD Implementation |
| Currently the SEAD/DEAD column is manually populated in the spread sheet after creation. This value is based on Opt/Platform's probability to penetrate (PTP) but there is no established fixed rule for determing the value. |
| Adaptive |
| Config Maint |
| Auto-checkout AC final |
| The users have requested the capability to automatically check out the associated AC final configuration, if necessary, when they merge PA/Gen Tms in WebAWPS. |
| Adaptive |
| Web AWPS |
| Additional Web AWPS data sources |
| The users would like to connect to more than just the PROD and PRP connections that are currently available. PC AWPS stored procedures are installed on several schemas, indicating user interest in those areas. As a minimum, the aircraft working schema. |
| Enhancement |
| Config Maint |
| Config Maint: Cannot check out empty config for read |
| Config Maint performs a check to see if there are new rows on the public schema. This was done to see if PA/Gen times had been added before checking out an aircraft config. However, if the public config is empty, it cannot be checked out for read/write. |
| Enhancement |
| Web AWPS |
| Additional information in confirmation message |
| Config Maintenance: Check out config. |
The confirmation message only asks if the user would like to check out the config. However, if the config is already checked out for write and has changes, the contents will be overwritten. Users request more detail.
| Enhancement |
| Decision Handbook |
| Web Decision Handbook - PACOM fields. |
| Need to determine how to populate PACOM fields in decision handbook. This may (probably) require new OM/COCOM fields in the EDB model. Fields are possibly based on Option/ Geo/ Functional attributes. |
| Enhancement |
| Config Maint |
| User friendly error messages in Web AWPS |
| When the user attempts to check-in a configuration with a status of "Private-Read", a very confusing error message is generated by the database. Buried in the listing of "ORAs" and other computerese is the phrase "Cfg <config n. |
| Enhancement |
| EADSIM |
| Web AWPS: Display the EADSIM laydown files on a map |
| Display the laydown files used for input to EADSIM on the map. These files include: r.lay, m.lay, a.lay, t.lay, c.lay, ICSL, ACCM, and RECCE laydown files. This also includes the B-2 .fpdf files. 1. Change map graphics for EDBLayerWidgets (R:0, D: |
| Enhancement |
| Web AWPS |
| Resource Impact: Upgrade Defined Options. |
| In Web AWPS - Resource Impact. Add option to Defined Option that is child of another option. The parent option is removed from the available list. Provide the capability to upgrade the child option to the parent option. |
| Enhancement |
| Web AWPS |
| Resource Impct: Default Degrade chart to COA country. |
| Start Web AWPS and go to Resource Impact. Add Options to COA Definitions and go to dashboard. Currenty Degrade chart defaults to arbitrary country. Enhancement is to default the Degrade chart country selection to the Country of the Defined Options. |
| Enhancement |
| Web AWPS |
| Resource Impct: Option charts weapon count axis is decimal. |
| Start Web AWPS and go to Resource Impact. Add Options to COA Definitions and go to dashboard. Currenty Option specific charts are displaying counts as decimal (i.e 0.5, 1.0, etc.). Change charts to display as integer, with minimum count of 4. |
| Enhancement |
| Web AWPS |
| Resource Impact - Implement swap/swing activation of target packages. |
| Web AWPS->Resource Impact. |
Provide the capability to replace an active target package with a corresponding swap/swing target package during the simulation.
| Enhancement |
| AWPS |
| Related Option Deviation Identification. |
| Provide the capability to identify differences (specifically targets hit, inlining, etc. ) in execution between related options. |
| Enhancement |
| Decision Handbook |
| Web AWPS - Plan Detail Print/Publish capability |
| Start Web AWPS - Plan Maintenance. Drill down to specific option. User requests capability to print detailed information on specific option. |
| Enhancement |
| MAP |
| Web Map Search - Publish/Print |
| Start Web AWPS. Open a map and search. |
Enhancement: Provide a publish/print capability for the search results.
| Enhancement |
| Web AWPS |
| Web AWPS: F5 Key refreshes browsers. |
| Start Web AWPS. Log in and begin tasks. Hit F5 key. The application is restarted requiring user to re-login. |
This is a feature of the browser and potentially no viable/secure solution could be available.
| Enhancement |
| Web AWPS |
| Connect Web AWPS to working versions of weapon configurations |
| Allow Web AWPS to connect to working versions of configurations such as Aircraft Working. |
| Enhancement |
| MAP |
| Web- Add weapon and booster from outside the circle search from the selected Option |
| Web Awps Maps - In the Circle Search details page, add the weapons/booster (weapons outside the circle search) from the selected option. It should be displayed in a way to know if it's inside the circle or outside. |
| Enhancement |
| MAP |
| Web- Add more detail on the Output page of the Circle Search Function. |
| Web Awps Maps - Part 1 of the report (damage expenctancy detail), add all the search criteria used to generate this data (location, search radius, r95, etc). Also state which option, DGZ, Facility and weapon were used for the comparison. |
| Enhancement |
| Decision Handbook |
| Generation Times for Aircraft in Decision Handbook |
| Allow the user to enter a default Generation time for Aircraft Options in the Web Decision Handbook. |
| Enhancement |
| Decision Handbook |
| Modify Decision Handbook for Overflight data |
| Web AWPS should report "Always", "Sometimes", and "Never" in the DH. |
Check to see if the grid should contain data for those values, too.
| Enhancement |
| Config Maint |
| Additional information in confirmation message |
| Config Maintenance: Check out config. |
The confirmation message only asks if the user would like to check out the config. However, if the config is already checked out for write and has changes, the contents will be overwritten. Users request more detail.
| Enhancement |
| C of E |
| Modify Mission Alert Status Code |
| The user would like the capability to modify a mission's alert status code. |
Design considerations:
Since the mission list is based on the alert cats, this is a major change that affects retrieval and DE calculations. Both client and server side impacts.
ATCH 18, WORK BREAKDOWN STRUCT
Sec J, Attachment 18: Work Breakdown Structure
Clin 0001
Operations and Maintenance
| 1.0 |
| Subsystem Software/Hardware Maintenance Year N - 1 |
1.1
Software Sustainment Technical Effort for Yr N - 1
1.11
Software Sustainment Technical Effort/Delivery # N-1
1.111
Code SCRs
1.12
Software Sustainment Technical Effort/Delivery # N-2
1.121
Code SCRs
1.13
Software Sustainment Technical Effort/Delivery # N-3
1.131
Code SCRs
1.14
Software Sustainment Functional
1.141
Year N Other Code Development
1.1411
- Unit Test
1.1412
- Code Reviews
1.1413
- Defect Workoff
1.142
Year N Detail Design
1.143
Year N System Engineering
1.144
Year N Database
1.145
Year N Data/CDRLs
1.146
Year N Information Assurance
1.147
Year N Configuration Mgmt/Data Mgmt
1.148
Year N Quality Assurance
1.149
Year N Product Integration
1.1491
- Product Integration SCR Workoff
1.15
Year N System Test
1.151
- System Test SCR Workoff
1.152
- CDT&E
1.153
- GDT&E
1.16
Year N Training
1.17
Program Management Office
1.171
Year N Prog Management
1.172
Year N Prog Administration
1.173
Year N Subcontract
1.174
Year N Security
1.175
Year N Contacts
1.176
Year N Chief Architect
1.177
Year N Chief Engineer/Task Lead
1.178
Year N Financial Management
1.179
Year N System Administration
Clin 0002
Other Direct Costs
2.1
Year N ODCs
2.11
- Year N OCCY/IT
2.12
- Year N Travel
2.13
| - Year N |
| Computer Administration |
2.14
- Year N Proposal Preparation
Clin 0003
Development Task Orders
| 3.0 |
| Subsystem Software/Hardware Maintenance Year N - 1 |
3.1
Software Sustainment Technical Effort for Yr N - 1
3.11
Software Sustainment Technical Effort/Delivery # N-1
3.111
Code SCRs
3.12
Software Sustainment Technical Effort/Delivery # N-2
3.121
Code SCRs
3.13
Software Sustainment Technical Effort/Delivery # N-3
3.131
Code SCRs
3.14
Software Sustainment Functional
3.141
Year N Other Code Development
3.1411
- Unit Test
3.1412
- Code Reviews
3.1413
- Defect Workoff
3.142
Year N Detail Design
3.143
Year N System Engineering
3.144
Year N Database
3.145
Year N Data/CDRLs
3.146
Year N Information Assurance
3.147
Year N Configuration Mgmt/Data Mgmt
3.148
Year N Quality Assurance
3.149
Year N Product Integration
3.1491
- Product Integration SCR Workoff
3.15
Year N System Test
3.151
- System Test SCR Workoff
3.152
- CDT&E
3.153
- GDT&E
3.16
Year N Training
3.17
Program Management Office
3.171
Year N Prog Management
3.172
Year N Prog Administration
3.173
Year N Subcontract
3.174
Year N Security
3.175
Year N Contacts
3.176
Year N Chief Architect
3.177
Year N Chief Engineer/Task Lead
3.178
Year N Financial Management
3.179
Year N System Administration
Clin 0004
Enhancement Task Orders (3400)
| 4.0 |
| Subsystem Software/Hardware Maintenance Year N - 1 |
4.1
Software Sustainment Technical Effort for Yr N - 1
4.11
Software Sustainment Technical Effort/Delivery # N-1
4.111
Code SCRs
4.12
Software Sustainment Technical Effort/Delivery # N-2
4.121
Code SCRs
4.13
Software Sustainment Technical Effort/Delivery # N-3
4.131
Code SCRs
4.14
Software Sustainment Functional
4.141
Year N Other Code Development
4.1411
- Unit Test
4.1412
- Code Reviews
4.1413
- Defect Workoff
4.142
Year N Detail Design
4.143
Year N System Engineering
4.144
Year N Database
4.145
Year N Data/CDRLs
4.146
Year N Information Assurance
4.147
Year N Configuration Mgmt/Data Mgmt
4.148
Year N Quality Assurance
4.149
Year N Product Integration
4.1491
- Product Integration SCR Workoff
4.15
Year N System Test
4.151
- System Test SCR Workoff
4.152
- CDT&E
4.153
- GDT&E
4.16
Year N Training
4.17
Program Management Office
4.171
Year N Prog Management
4.172
Year N Prog Administration
4.173
Year N Subcontract
4.174
Year N Security
4.175
Year N Contacts
4.176
Year N Chief Architect
4.177
Year N Chief Engineer/Task Lead
4.178
Year N Financial Management
4.179
Year N System Administration
Clin 0005
DATA
Not Separately Priced
Clin 0006
Target SLBM Stage III (Sample Task)
| 6.0 |
| Subsystem Software/Hardware Maintenance Year N - 1 |
6.1
Software Sustainment Technical Effort for Yr N - 1
6.11
Software Sustainment Technical Effort/Delivery # N-1
6.111
Code SCRs
6.12
Software Sustainment Technical Effort/Delivery # N-2
6.121
Code SCRs
6.13
Software Sustainment Technical Effort/Delivery # N-3
6.131
Code SCRs
6.14
Software Sustainment Functional
6.141
Year N Other Code Development
6.1411
- Unit Test
6.1412
- Code Reviews
6.1413
- Defect Workoff
6.142
Year N Detail Design
6.143
Year N System Engineering
6.144
Year N Database
6.145
Year N Data/CDRLs
6.146
Year N Information Assurance
6.147
Year N Configuration Mgmt/Data Mgmt
6.148
Year N Quality Assurance
6.149
Year N Product Integration
6.1491
- Product Integration SCR Workoff
6.15
Year N System Test
6.151
- System Test SCR Workoff
6.152
- CDT&E
6.153
- GDT&E
6.16
Year N Training
6.17
Program Management Office
6.171
Year N Prog Management
6.172
Year N Prog Administration
6.173
Year N Subcontract
6.174
Year N Security
6.175
Year N Contacts
6.176
Year N Chief Architect
6.177
Year N Chief Engineer/Task Lead
6.178
Year N Financial Management
6.179
Year N System Administration
Clin 0007
On-Site Representation
| 7.1 |
| On-site Representation |
7.11
Service Task
Clin 0008
FFP Task Orders
| 8.0 |
| Subsystem Software/Hardware Maintenance Year N - 1 |
8.1
Software Sustainment Technical Effort for Yr N - 1
8.11
Software Sustainment Technical Effort/Delivery # N-1
8.111
Code SCRs
8.12
Software Sustainment Technical Effort/Delivery # N-2
8.121
Code SCRs
8.13
Software Sustainment Technical Effort/Delivery # N-3
8.131
Code SCRs
8.14
Software Sustainment Functional
8.141
Year N Other Code Development
8.1411
- Unit Test
8.1412
- Code Reviews
8.1413
- Defect Workoff
8.142
Year N Detail Design
8.143
Year N System Engineering
8.144
Year N Database
8.145
Year N Data/CDRLs
8.146
Year N Information Assurance
8.147
Year N Configuration Mgmt/Data Mgmt
8.148
Year N Quality Assurance
8.149
Year N Product Integration
8.1491
- Product Integration SCR Workoff
8.15
Year N System Test
8.151
- System Test SCR Workoff
8.152
- CDT&E
8.153
- GDT&E
8.16
Year N Training
8.17
Program Management Office
8.171
Year N Prog Management
8.172
Year N Prog Administration
8.173
Year N Subcontract
8.174
Year N Security
8.175
Year N Contacts
8.176
Year N Chief Architect
8.177
Year N Chief Engineer/Task Lead
8.178
Year N Financial Management
8.179
Year N System Administration
Clin 0009
Transition Support
| 9.0 |
| Year N Transition Support |
9.1
Transition Support (First and final Year)
ATCH 3, DD FORM 254
Sec J, Attachment 3: DD254
DEPARTMENT OF DEFENSE
CONTRACT SECURITY CLASSIFICATION SPECIFICATION
(The requirements of the DoD Industrial Security Manual apply to all security aspects of this effort.)
1. CLEARANCE AND SAFEGUARDING
a. FACILITY CLEARANCE REQUIRED
Top Secret
b. LEVEL OF SAFEGUARDING REQUIRED
Top Secret
| 2. THIS SPECIFICATION IS FOR: (x and complete as applicable) |
| 3. THIS SPECIFICATION IS: (x and complete as applicable) |
FORMCHECKBOX
a. PRIME CONTRACT NUMBER
FORMCHECKBOX
| a. ORIGINAL (Complete date in all cases) |
| DATE (YYMMDD) |
110708
FORMCHECKBOX
b. SUBCONTRACT NUMBER
FORMCHECKBOX
b. REVISED (Supersedes all previous specs)
| Revision No. |
| DATE (YYMMDD) |
FORMCHECKBOX
c. SOLICITATION OR OTHER NUMBER
FA4600-11-R-0006
DUE DATE (YYMMDD)
XXXXXX
FORMCHECKBOX
| c. FINAL (Complete Item 5 in all cases) |
| DATE (YYMMDD) |
4. THIS IS A FOLLOW-ON CONTRACT? FORMCHECKBOX
YES FORMCHECKBOX
NO. If Yes, complete the following:
Classified material received or generated under (Preceding Contract Number) is transferred to this follow-on contract.
5. IS THIS A FINAL DD FORM 254? FORMCHECKBOX
YES FORMCHECKBOX
NO. If Yes, complete the following:
In response to the contractor’s request dated , retention of the identified classified material is authorized for the period of
6. CONTRACTOR (Include Commercial and Government Entity (CAGE) Code)
a. NAME, ADDRESS, AND ZIP CODE
XXXXXX
| b. CAGE CODE |
| c. .COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code) |
7. SUBCONTRACTOR
a. NAME, ADDRESS, AND ZIP CODE
XXXXXX
| b. CAGE CODE |
| c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip code) |
8. ACTUAL PERFORMANCE
a. LOCATION
XXXXXX
| b. CAGE CODE |
| c. COGNIZANT SECURITY OFFICE(Name, Address, and Zip Code) |
9. GENERAL IDENTIFICATION OF THIS PROCUREMENT
Automated Windows Planning System (AWPS) is a force-level mission planning system with full fidelity planning functions in support of the nation’s nuclear war plan. AWPS will be supported under the MPACS contract. The MPACS contract will consist of one base year plus four option years. Start date will be entered on award.
| 10. THIS CONTRACT WILL REQUIRE ACCESS TO: |
| YES |
| NO |
| 11. IN PERFORMING THIS CONTRACT, THE CONTRACTOR WILL: |
| YES |
| NO |
| a. COMMUNICATIONS SECURITY (COMSEC) INFORMATION |
| FORMCHECKBOX |
FORMCHECKBOX
a. HAVE ACCESS TO CLASSIFIED INFORMATION ONLY AT ANOTHER CONTRACTOR’S
FACILITY OR A GOVERNMENT ACTIVITY
FORMCHECKBOX
FORMCHECKBOX
| b. RESTRICTED DATA |
| FORMCHECKBOX |
FORMCHECKBOX
| b. RECEIVE CLASSIFIED DOCUMENTS ONLY |
| FORMCHECKBOX |
FORMCHECKBOX
| c. CRITICAL NUCLEAR WEAPON DESIGN INFORMATION |
| FORMCHECKBOX |
FORMCHECKBOX
| c. RECEIVE AND GENERATE CLASSIFIED MATERIAL |
| FORMCHECKBOX |
FORMCHECKBOX
| d. FORMERLY RESTRICTED DATA |
| FORMCHECKBOX |
FORMCHECKBOX
| d. FABRICATE, MODIFY, OR STORE CLASSIFIED HARDWARE |
| FORMCHECKBOX |
FORMCHECKBOX
| e. INTELLIGENCE INFORMATION: |
| FORMCHECKBOX |
FORMCHECKBOX
| e. PERFORM SERVICES ONLY |
| FORMCHECKBOX |
FORMCHECKBOX
| (1) Sensitive Compartmented information (SCI) |
| FORMCHECKBOX |
FORMCHECKBOX
f. HAVE ACCESS TO U.S. CLASSIFIED INFORMATION OUTSIDE THE U.S., PUERTO RICO, U.S. POSSESSIONS AND TRUST TERRITORIES
FORMCHECKBOX
FORMCHECKBOX
| (2) Non-SCI |
| FORMCHECKBOX |
FORMCHECKBOX
g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE TECHNICAL INFORMATION
CENTER (DTIC) OR OTHER SECONDARY DISTRIBUTION CENTER
FORMCHECKBOX
FORMCHECKBOX
| f. SPECIAL ACCESS INFORMATION |
| FORMCHECKBOX |
FORMCHECKBOX
| h. REQUIRE A COMSEC ACCOUNT |
| FORMCHECKBOX |
FORMCHECKBOX
| g. NATO INFORMATION |
| FORMCHECKBOX |
FORMCHECKBOX
| i. HAVE TEMPEST REQUIREMENTS |
| FORMCHECKBOX |
FORMCHECKBOX
| h. FOREIGN GOVERNMENT INFORMATION |
| FORMCHECKBOX |
FORMCHECKBOX
| j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS |
| FORMCHECKBOX |
FORMCHECKBOX
| i. LIMITED DISSEMINATION INFORMATION |
| FORMCHECKBOX |
FORMCHECKBOX
| k. BE AUTHORIZED TO USE THE DEFENSE COURIER SERVICE |
| FORMCHECKBOX |
FORMCHECKBOX
| j. FOR OFFICIAL USE ONLY INFORMATION |
| FORMCHECKBOX |
FORMCHECKBOX
l. OTHER (Specify)
SIPRNet
FORMCHECKBOX
FORMCHECKBOX
k. OTHER (Specify)
NC2-ESI,
FORMCHECKBOX
FORMCHECKBOX
DD FORM 254, DEC 1999
12. PUBLIC RELEASE. Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the iNISPOM or unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release
FORMCHECKBOX
Direct FORMCHECKBOX Through (Specify):
901 SAC Boulevard Suite 1A1 (See DD Form 254 Continuation Sheets for SCI comments)
Offutt AFB NE 68113-6020
"Public Release By Private Parties" to the Directorate for Freedom of Information and Security Review, Office of the Assistant Secretary of Defense (Public Affairs)* for review.
*In the case of non-DoD User Agencies, requests for disclosure shall be submitted to that agency.
13. SECURITY GUIDANCE. The security classification guidance needed for this classified effort is identified below. If any difficulty is encountered in applying this guidance or if any other contributing factor indicates a need for changes in this guidance, the contractor is authorized and encouraged to provide recommended changes; to challenge the guidance or the classification assigned to any information or material furnished or generated under this contract; and to submit any questions for interpretation of this guidance to the official identified below. Pending final decision, the information involved shall be handled and protected at the highest level of classification assigned or recommended. (Fill in as appropriate for the classified effort. Attach, or forward under separate correspondence, any documents/guides/extracts referenced herein. Add additional pages as needed to provide complete guidance.)
Reference Item 1.
This contract will involve handling and storage of classified material. Contractor has responsibility for alarmed areas (except SCI facilities unless approved by J2113) and properly escorting both contractor and government personnel (except SCI facilities unless approved by J2113). Contractor is directly accountable for security actions and government rule compliance to include COMSEC and OPSEC requirements. Contractors will be subject to investigation and potential adverse action in the event of security deviations and violations.
Reference Item 8a.
The contract will be performed at Offutt AFB NE and at contractor location/s XXXXXXXXXXXXX.
See DD Form 254 Continuation Sheets for additional security guidance.
Coordination: J050 _____ J841 _____ J2112 _____ 55 CONS _____ J834 _____ J32 _____ PSO AFOSI Region 7/OL-C _____
14. ADDITIONAL SECURITY REQUIREMENTS. Requirements, in addition to NISPOM requirements, are established for this contract. (If Yes, identify the FORMCHECKBOX Yes FORMCHECKBOX No pertinent contractual clauses in the contract document itself, or provide any appropriate statement which identifies the additional requirements. Provide a copy of the requirements to the cognizant security office. Use Item 13 if additional space is needed.)
Visitor Group Contractors are required to enter into a security agreement with the host base information security program manager. Provide
The information requested by the notification of Government Security Activity Clause, AFFARS 5352.204-9000, and Visitor Group Security
Agreement Clause, AFFARS 5352.204-9001, to the Servicing Security Activity (SSA). Cont in Sec 13/continuation sheet
15. INSPECTIONS. Elements of this contract are outside the inspection responsibility of the cognizant security office. (If Yes, explain and identify specific FORMCHECKBOX Yes FORMCHECKBOX No areas or elements carved out and the activity responsible for inspections. Use Item 13 if additional space is needed.)
When contractors are designated as Visitor Groups on Air Force installations, Industrial Security Reviews for collateral information will be conducted by the host base SSA. DSS will have inspection oversight of the contractor’s off-base facilities. The Defense Security Service (DSS) is relieved of inspection responsibilities for contract activities at USSTRATCOM not involving SCI access. USSTRATCOM/J050 will conduct Information Security Program Reviews biennially to ensure compliance with the NISPOM, DoD 5200.1-R, Strategic Instructions, and the Visitor Group Security Agreement. (See DD Form 254 Con't Sheets)
16. CERTIFICATION AND SIGNATURE. Security requirements stated herein are complete and adequate for safeguarding the classified information to be released or generated under this classified effort. All questions shall be referred to the official named below.
a. TYPED NAME OF CERTIFYING OFFICIAL
Cheryl Haun
b. TITLE
Contracting Officer
c. TELEPHONE (Include Area Code)
(402) 294-7304
d. ADDRESS (Include Zip Code)
55 CONS/LGCZ
101 Washington Square
Offutt AFB NE 68113-2107
17. REQUIRED DISTRIBUTION
FORMCHECKBOX
a. CONTRACTOR
FORMCHECKBOX
b. SUBCONTRACTOR
FORMCHECKBOX
c. COGNIZANT SECURITY OFFICE FOR PRIME AND SUBCONTRACTOR
FORMCHECKBOX
d. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY ADMINISTRATION
FORMCHECKBOX
e. ADMINSTRATIVE CONTRACTING OFFICER
FORMCHECKBOX
f. OTHERS AS NECESSARY
e. SIGNATURE
DD FORM 254 (BACK), DEC 1999
Continuation Sheet for DD Form 254 for Contract No XXXXXXXXXXXXXX
Reference Item 6a. , 6b. , and 6c.
Additional contractor address, Cage Code, and Cognizant Security Office:
Company Name of Contractor (Cage Code)
Cognizant Security Office Street Address
Street Address
City, State, and Zip Code
City, State, and Zip Code Reference Item 8c, Contractor may be required to support SAP programs and provide cleared facilities.
Note: The USSTRATCOM Special Access Program Security Manager (SAPSM) is the cognizant security office for all SAPs related to this contract. HQ USSTRATCOM/ SAPSM is located at 901 SAC Blvd. STE M121, Offutt AFB NE 68113. The USSTRATCOM SAPSM is located in Bldg #501, Room M121, telephone number is comm 402-294-3055 and/or DSN 271-3055.
Reference Item 10a.
COMSEC material/information may not be released to DoD contractors without Air Force Cryptological Support Center (AFCSC) approval. Contractor must forward request for COMSEC material/information to the COMSEC officer through the Program Office. The contractor is governed by the DoD 5220.00-S COMSEC supplement to the NISPOM on the control and protection of COMSEC material /information. Access to COMSEC material/information by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances.
Reference Item 10b. Contractor may require access to RESTRICTED DATA. Access to RESTRICTED DATA requires a final US Government clearance at the appropriate level.
Reference Item 10c. The contractor is permitted access to CNWDI in performance of this contract. Access to CNWDI requires a final US Government clearance at the appropriate level and contractor personnel must be briefed for CNWDI prior to access.
Reference Item 10d. Access to Formerly Restricted Data requires a final US Government clearance at the appropriate level.
Reference Item 10e. Access to Intelligence Information requires a final US Government clearance at the appropriate level. Prior approval of the contracting activity is required for sub-contracting.
Reference Item 10e.(1):
a) Intelligence Information Sensitive Compartmented Information (SCI) is required for contractor personnel in the (Room No.) SCIF, the (Room No.) SCIF, and at xxxxxxxxxxxxxxxxxxxx distributed sites.
b) The Command Foreign Disclosure and Special Security Office (J211) is designated as the responsible security office for the SCI elements of the contract. DIA is responsible for security oversight of the SCI elements of this contract while DSS retains oversight for the collateral elements that are performed off Offutt AFB NE.
c) Instructions for access to SCI are as follows:
1) All SCI will be handled in accordance with special security requirements furnished by the responsible Special Security Office designated above.
2) The contractor shall provide J211 through the contract monitor, a list of all employees performing work on the contract who require SCI access. The chief of the division where contractor employees are working will certify need-to-know for SCI access.
3) SCI will not be released to contractor personnel without specific release approval of the USSTRATCOM Senior Intelligence Official or the originator of the material, when applicable, obtained through J211, J512 based on prior approval and certification of "Need to Know" by the appropriate Division Chief through the designated contract monitor.
4) Inquiries pertaining to classification guidance on SCI will be directed to the responsible contract monitor. Any SCI or SCI derived material generated under this contract shall be reviewed by the contract monitor for proper SCI classification prior to final publication and distribution. The responsible Special Security Office designated above will provide assistance as required.
5) SCI furnished in support of this contract remains the property of the DoD department, agency or command that releases it. Upon completion or cancellation of the contract, all SCI furnished will be returned to the direct custody of the responsible Special Security Office designated above. See DoD 5105.21-M-1 for complete guidance of handling SCI.
6) All work on SCI material will be done within a SCI Facility (SCIF) on Offutt AFB or Government-approved contractor SCIF, or other Government-approved SCI facility.
7) National Interest Determination (NID). The Community Acquisition Risk Section (CARS), on behalf of the Director of National Intelligence, letter to the 55 CONS/LGCZ, dated xx xxx xx, approved the requested NID for (Company name of contractor).
8) Designated contract monitor is:
Perry Wilson, ESC/HSBB, (402) 294-8260
Reference Item 10e.(2): The following requirements and controls apply to classified foreign intelligence.
a) Requests for release of classified foreign intelligence information are prepared by the contractor and submitted to USSTRATCOM / J2S through the contracting agency. Each request for release of intelligence must contain the following information and clarification.
1) Name and address of the contractor for whom the intelligence is intended and certification by the contracting activity of the clearance and safeguarding capability.
Company Name of Contractor
Street Address
City, State, and Zip Code
2) Contract number and length of contract: XXXXXXXXXXXXX, (Expiration date).
3) Name of the contracting activity, their certification of need-to-know, and name and telephone number of a point of contact.
55 CONS/LGCZ
101 Washington Square
Offutt AFB NE 68113-2107
Need to know will be certified by the appropriate certification authority via the contract monitor.
Designated contract monitors are the points of contact.
Perry Wilson, ESC/HSBB, (402) 294-8260
4) Complete identification of the intelligence for which release approval is requested. Identify issuing agency, security classification, and all restrictive control markings and statements. Also include a statement as to whether the material is locally available to the requestor.
5) A description of the contractor work for which the intelligence is required. Include sufficient detail so J2S can determine all of the intelligence information the contractor needs.
6) Contractor tasks are specified in the applicable portion of the Performance Work Statement (PWS).
CONTRACTOR CONTROLS FOR CLASSIFIED FOREIGN INTELLIGENCE
a) The contractor shall maintain accountability for all classified foreign intelligence released to its custody (includes Confidential Information).
b) The contractor shall not reproduce classified foreign intelligence without the written permission of the releasing agency. If permission is granted, each copy will be controlled in the same manner as the original.
c) The contractor must not destroy any classified foreign intelligence without the written permission of the releasing agency.
d) The contractor shall restrict access to only those individuals who possess the necessary security clearance and who are actually providing services under the contract. Further dissemination to other contractors, subcontractors, other government agencies, private individuals, or organizations is prohibited unless authorized in writing by the releasing agency.
e) Classified foreign intelligence must not be released to foreign nationals or immigrant aliens, whether or not they are also consultants, U.S. contractors or employees of the contractor, and regardless of the level of their security clearance, except with the written permission of the originator.
f) The contractor must ensure that each employee having access to classified foreign intelligence material is fully aware of the special security requirements for this material and shall maintain records in a manner that will permit the contractor to furnish, on demand, the names of individuals who have had access to the material in the contractor's custody.
g) Upon completion or termination of the classified contract, or sooner when the purpose of the release has been served, the contractor shall return all classified foreign intelligence (furnished or generated), unless retention or destruction is authorized in writing by originator or USSTRATCOM / J211, J512
Reference Item 10(f)
a) This contract may be permitted access to classified information/material up to and including TOP SECRET and TOP SECRET/SAP in performance of this contract. The contractor may require access to SAP programs and data to develop analytical methodologies, support services, modeling applications, or intelligence support to enhance integrated effects. Contractor's identified as having a requirement for this level of access must have a need to know and provide a reoccurring material contribution to the success of the program/operation. All elements of this contract for SAP information or material are under the cognizance of the HQ USSTRATCOM SAPCO.
b) Requests for SAP access will be made through the local PSM or APS Program Manager. The security clearance requirement for this contract is a final Top Secret clearance based on a SSBI investigation within the last five years. Personnel nominated for program access must submit their personnel security questionnaire, eQIP, or Standard Form 86, current within one year, to USSTRATCOM / J32 for program access eligibility screening submission.
c) Continued contractor access requires initial and recurring annual SAP security education training. The PSM/PM will conduct the training at the location where the contractor's program access records are kept.
d) Inquiries regarding SAP classification guidance will be directed to the Program Security Office (PSO), PSM, or PM. Any SAP-derived material generated under this contract will be reviewed by the PSO, PSM, or PM for proper classification prior to final publication, distribution, or transmission.
e) SAP information furnished or generated in support of this contract remains the property of the Government and will be returned to the servicing program office upon completion of this contract.
f) All procedures, equipment, and devices used for data processing or data transfer of SAP information must be accredited (approved) by the PSO before any processing is permitted. Any subsequent configuration or procedural changes must also be approved prior to use.
g) The contractor may produce classified material and have access to classified data/areas listed in Item 8.a. only.
h) The government will provide adequate classified storage capability. Only properly accessed (program briefed) personnel will have access to security containers and classified media containing SAP information.
i) National Interest Determination (NID). SAF/AAZ letter to the 55 CONS/LGCZ, dated xx xxx xx, approved the requested NID for (Company name of contractor).
Reference Item 10g.
a) Contractor will require access to North Atlantic Treaty Organization (NATO) Top Secret information for reference only at USSTRATCOM. This means information belonging to, and circulated by, NATO. Prior approval of the contracting activity is required for subcontracting. Special briefings are required and access to classified NATO information requires a final U.S. Government clearance at the appropriate level.
Re…
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 .